Cingular must be hiring high school kids to do their web site, because it seems to be about as robust as Michael Jackson's defense.
Every time I try to log in to their web site, I have to try three times, because the first two inevitably fail with an error saying "our site it having trouble accessing your records, try again in a few minutes".
Today, I went it to verify my list of features to make sure the "Roadside Assistance" plan is outta there. I managed to check the first two lines, but when I check the third and fourth, I'm getting a rather unfriendly and unprofessional null pointer exception from their web site:
Error 500--Internal Server Error |
java.lang.NullPointerException
at com.cingular.olam.webcomponent.servlets.AddFeaturesToCurrentPPWA.service
(AddFeaturesToCurrentPPWA.java:284)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:301)
at com.cingular.olam.webcomponent.servlets.DispatcherServlet.ForwardToPage(DispatcherServlet.java:58)
at com.cingular.olam.webcomponent.servlets.DispatcherServlet.service(DispatcherServlet.java:30)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run
(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
|
Any web doofus should know that you NEVER expose Java errors and tracebacks directly to end users. Java supports exception handling, but these guys must not know that. Wouldn't it be fun if this traceback included information that hackers could use to break in?
So much for being a "technology company".
