search

LiTiang / js-test-driver

Automatically exported from code.google.com/p/js-test-driver
0 stars 0 forks source link

Intermittent NullPointerException when running tests #154

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When running our jstests against firefox, occasionally (maybe 1 in 3 times), 
the process fails with the following exception:

java.lang.NullPointerException
[11:30:56]: [Exec]  at 
com.google.jstestdriver.CommandServlet.service(CommandServlet.java:133)
[11:30:56]: [Exec]  at 
com.google.jstestdriver.CommandServlet.doPost(CommandServlet.java:122)
[11:30:56]: [Exec]  at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
[11:30:56]: [Exec]  at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
[11:30:56]: [Exec]  at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
[11:30:56]: [Exec]  at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
[11:30:56]: [Exec]  at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
[11:30:56]: [Exec]  at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
[11:30:56]: [Exec]  at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
[11:30:56]: [Exec]  at org.mortbay.jetty.Server.handle(Server.java:326)
[11:30:56]: [Exec]  at 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
[11:30:56]: [Exec]  at 
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
[11:30:56]: [Exec]  at 
org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
[11:30:56]: [Exec]  at 
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
[11:30:56]: [Exec]  at 
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
[11:30:56]: [Exec]  at 
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
[11:30:56]: [Exec]  at 
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)

I have attached the complete test log with debug output. Any help on this would 
be greatly appreciated!

Original issue reported on code.google.com by willhol...@gmail.com on 29 Oct 2010 at 12:05

Attachments:

GoogleCodeExporter commented 9 years ago 
Hopefully fixed in 1.3.0

Original comment by corbinrs...@gmail.com on 14 Feb 2011 at 4:23