looking for flights from Lima to Tarapoto Peru, set Lima in the From drop down, the clicked the radio button “One way”, and the “To:” drop down box goes away and a waiting animated graphic appears infinitely. Reloading the page, if you select your origin and stay away from the radios (round trip and one way leaving the default to round trip), the destination drop down appears.
This happened in Firefox, Chrome, and IE 8.
Using Google Chrome in Windows XP Pro, enter a roundtrip from PDX to Lima, Peru depart 12/22, return 1/3 and it gives a validation error that city name can’t contain numbers in the destination (Lima) — but there are NO numbers in “Lima”.
The destination field background becomes red.
I can only gather that they don’t fly to Peru.
Once again today registering a domain at Google Apps shows initially the domain will be registered through one Registrar, then on subsequent page terms are presented for a different registrar.
When registering for a new domain today, the initial new domain reg form showed it would be registered via GoDaddy, but upon going to the next page the checkbox to agree to terms of service was for Enom. Reloading the back, going back and forth in the browser a few times got me to the form having GoDaddy in both places.
browser: Google Chrome
OS: Windows XP Pro
The following website bug loading one of our customers pages found in a Google search on this website:
Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: fiid is null in html_header.jsp
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:460)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:355)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToPage(TransactionProcessorServlet.java:1403)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToErrorPage(TransactionProcessorServlet.java:1294)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToErrorPage(TransactionProcessorServlet.java:1281)
com.premier.ofa.servlets.TransactionProcessorServlet.doGet(TransactionProcessorServlet.java:853)
com.premier.ofa.servlets.TransactionProcessorServlet.doPost(TransactionProcessorServlet.java:693)
javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
com.premier.ofa.servlets.TransactionProcessorServlet.service(TransactionProcessorServlet.java:157)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
root cause
javax.servlet.ServletException: fiid is null in html_header.jsp
org.apache.jsp.jsp.displaycriticalerror_jsp._jspService(displaycriticalerror_jsp.java:286)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToPage(TransactionProcessorServlet.java:1403)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToErrorPage(TransactionProcessorServlet.java:1294)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToErrorPage(TransactionProcessorServlet.java:1281)
com.premier.ofa.servlets.TransactionProcessorServlet.doGet(TransactionProcessorServlet.java:853)
com.premier.ofa.servlets.TransactionProcessorServlet.doPost(TransactionProcessorServlet.java:693)
javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
com.premier.ofa.servlets.TransactionProcessorServlet.service(TransactionProcessorServlet.java:157)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.27 logs.
Apache Tomcat/5.5.27
this teetered around session expiry, bug on screen as follows:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:433)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToPage(TransactionProcessorServlet.java:1403)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToErrorPage(TransactionProcessorServlet.java:1294)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToErrorPage(TransactionProcessorServlet.java:1281)
com.premier.ofa.servlets.TransactionProcessorServlet.doGet(TransactionProcessorServlet.java:853)
com.premier.ofa.servlets.TransactionProcessorServlet.doPost(TransactionProcessorServlet.java:693)
javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
com.premier.ofa.servlets.TransactionProcessorServlet.service(TransactionProcessorServlet.java:157)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
root cause
java.lang.NullPointerException
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.27 logs.
Apache Tomcat/5.5.27
Was entering a date range for about a year ago at selco.org, left the screen for maybe 10 minutes, came back, was not logged out, went back to enter a date range and the following bug occurred:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: fiid is null in html_header.jsp
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:460)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:355)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToPage(TransactionProcessorServlet.java:1403)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToErrorPage(TransactionProcessorServlet.java:1294)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToErrorPage(TransactionProcessorServlet.java:1281)
com.premier.ofa.servlets.TransactionProcessorServlet.doGet(TransactionProcessorServlet.java:853)
javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
com.premier.ofa.servlets.TransactionProcessorServlet.service(TransactionProcessorServlet.java:157)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
root cause
javax.servlet.ServletException: fiid is null in html_header.jsp
org.apache.jsp.jsp.displaycriticalerror_jsp._jspService(displaycriticalerror_jsp.java:286)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToPage(TransactionProcessorServlet.java:1403)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToErrorPage(TransactionProcessorServlet.java:1294)
com.premier.ofa.servlets.TransactionProcessorServlet.forwardToErrorPage(TransactionProcessorServlet.java:1281)
com.premier.ofa.servlets.TransactionProcessorServlet.doGet(TransactionProcessorServlet.java:853)
javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
com.premier.ofa.servlets.TransactionProcessorServlet.service(TransactionProcessorServlet.java:157)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.27 logs.
Apache Tomcat/5.5.27
As of the date of this posting, click You account link to login and login will hang indefinitely.
link:
http://www.bizrate.com/myaccount/login__url--/mybizrate/index.xpml.html
The URL looks funny enough to me that it makes sense there’s a problem…
After a few minutes it went to a blank page.
when logging into adsense.google.com if you have a cookie set, I think from adwords or another google account, then the login routine tries to auto log you in but loops infinitely – seen in the Chrome web browser, win xp pro.
Website Bugs
