Question
I have been encountering this Ebay error on selling lists on and off over the last week. It hasn't gone away, so I did a copy and paste of it here, to see what the computer literate think of it.
Just curious, Kevin
Error page exception
The server cannot use the error page specified for your application to handle the Original Exception printed below. Please see the Error Page Exception below for a description of the problem with the specified error page.
Original Exception:
Error Message: Failed to load target servlet [WebAppFrontController]
Error Code: 500
Target Servlet: WebAppFrontController
Error Stack:
java.lang.ClassNotFoundException: com.ebay.application.presentation.web.WebAppFrontC ontroller
at com.ibm.ws.classloader.CompoundClassLoader.findCla ss(CompoundClassLoader.java(Compiled Code))
at com.ibm.ws.classloader.CompoundClassLoader.loadCla ss(CompoundClassLoader.java(Compiled Code))
at java.lang.ClassLoader.loadClass(ClassLoader.java(C ompiled Code))
at java.beans.Beans.instantiate(Beans.java:201)
at java.beans.Beans.instantiate(Beans.java:62)
at com.ibm.ws.webcontainer.webapp.WebAppServletManage r.loadServlet(WebAppServletManager.java:188)
at com.ibm.ws.webcontainer.webapp.WebAppServletManage r.getServletReference(WebAppServletManager.java:45 5)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletRe ference(WebApp.java:652)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cherInfo.calculateInfo(WebAppRequestDispatcherInfo .java:172)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cherInfo.<init>(WebAppRequestDispatcherInfo.java:5 9)
at com.ibm.ws.webcontainer.webapp.WebApp.getRequestDi spatcher(WebApp.java:1462)
at com.ibm.ws.webcontainer.webapp.WebApp.getRequestDi spatcher(WebApp.java:1421)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleIn vocationHook(WebAppInvoker.java:268)
at com.ibm.ws.webcontainer.cache.invocation.CachedInv ocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcesso r.dispatchByURI(ServletRequestProcessor.java:182)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDis patcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handle Request(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleReques t(HttpConnection.java:618)
at com.ibm.ws.http.HttpConnection.run(HttpConnection. java:439)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:593)
Error Page Exception:
Error Message: Failed to load target servlet [ErrorDispatcher]
Error Code: 0
Target Servlet: null
Error Stack:
java.lang.ClassNotFoundException: com.ebay.application.presentation.web.WebErrorServ let
at com.ibm.ws.classloader.CompoundClassLoader.findCla ss(CompoundClassLoader.java(Compiled Code))
at com.ibm.ws.classloader.CompoundClassLoader.loadCla ss(CompoundClassLoader.java(Compiled Code))
at java.lang.ClassLoader.loadClass(ClassLoader.java(C ompiled Code))
at java.beans.Beans.instantiate(Beans.java(Compiled Code))
at java.beans.Beans.instantiate(Beans.java(Inlined Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebAppServletManage r.loadServlet(WebAppServletManager.java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebAppServletManage r.getServletReference(WebAppServletManager.java(Co mpiled Code))
at com.ibm.ws.webcontainer.webapp.WebApp.getServletRe ference(WebApp.java(Inlined Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cherInfo.calculateInfo(WebAppRequestDispatcherInfo .java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cherInfo.<init>(WebAppRequestDispatcherInfo.java(I nlined Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebApp.getErrorPage Dispatcher(WebApp.java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebApp.handleError( WebApp.java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebApp.sendError(We bApp.java(Inlined Compiled Code))
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForwar d(WebAppInvoker.java(Compiled Code))
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleIn vocationHook(WebAppInvoker.java(Compiled Code))
at com.ibm.ws.webcontainer.cache.invocation.CachedInv ocation.handleInvocation(CachedInvocation.java(Com piled Code))
at com.ibm.ws.webcontainer.cache.invocation.Cacheable InvocationContext.invoke(CacheableInvocationContex t.java(Compiled Code))
at com.ibm.ws.webcontainer.srp.ServletRequestProcesso r.dispatchByURI(ServletRequestProcessor.java(Compi led Code))
at com.ibm.ws.webcontainer.oselistener.OSEListenerDis patcher.service(OSEListener.java(Compiled Code))
at com.ibm.ws.webcontainer.http.HttpConnection.handle Request(HttpConnection.java(Compiled Code))
at com.ibm.ws.http.HttpConnection.readAndHandleReques t(HttpConnection.java(Compiled Code))
at com.ibm.ws.http.HttpConnection.run(HttpConnection. java(Compiled Code))
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava(Compiled Code))
Answer
See my replies in this thread:
http://www.auctionethics.com/ultimat...c;f=1;t=012597
My basic conclusion is that the memory of this WebSphere container is corrupt. You would normally not get these kinds of errors if the container has the correct classpath, and you have deployed your .ear file properly. My solution is to restart the container. They usually do this by taking machines out of the cluster and rebooting them once a week.
You will notice in this stack trace that application code has not yet been reached. The WebSphere java code is calling the JVM code, attempting to load the application. This is almost a certain sign of emory corruption, because if WebSphere and the java VM didn't work, many people would be complaining.
Answer
G'day Vinyl1,
In your opinion, if they have not done anything about it in a week, is it likely to lead to further problems?
Is it reasonable that a company as reliant on their servers as Ebay has not yet fixed it?
Still only curious, as a refresh almost always gets the correct page.
Cheers, Kevin
Answer
I think if a person were able to understand your answer to the problem they might have understood the error message to begin with. Sounds to me like the computer missed an exit and had to do a u-turn.
Answer
Well, picture this, Kevin.
At eBay, a single IP address leads to a router. A hardware load-balancer directs you to one of hundreds of webservers on hundreds of logical, if not physical servers. Each webserver rules over a cluster of WebSphere containers, maybe 20 or 30.
A single container in this vast array goes bad. A user gets an error message. The user hits 'refresh', and is connected to another webserver on another machine with another set of containers, and gets his page. He assumes it is a temporary glitch, and doesn't report it.
How long before anyone at eBay notices?
You could try to write an automated tester that checks each container every hour or so, but that would be really difficult.
Usually, they no one worries about stuff like this unless it becomes widespread, especially in a large organization. Ten or twenty users out of millions get an error, and then they refresh and don't get an error. This is considered tolerable.
Answer
I should also mention that strange glitches are a norm in this techology.
The day before yesterday, the guy in the next cubicle moved a new .ear file to production. When the programmer whose .ear file it was tested the application, he started getting strange errors that had not come up in testing.
When you deploy a .ear file at my place (Oracle appserver, not WebSphere), you stop the container. run the deployment command, and start the container.
We couldn't figure out what was causing the errors. Someone suggested we should try stopping the container and restarting it. We did, and it immediately started working correctly. Since we had stopped the container for the deployment, and allowed the deployment to complete before restarting, it should have worked the first time, but it didn't.
Answer
Kevin, it means that something isn't working properly.
Answer
If I read it correctly, we are safe so long as it does not become contagious.
Cheers, Kevin
Answer
I think IBM needs to make a fresh pot of coffee.
Blanche
Answer
Seems to me we have to crash the whole system in order for them to turn on and off all the devices.
I guess the simple approach of turning on and off the computer still works 99% of the time.