Community
Participate
Working Groups
Jetty 7.3.1 java.lang.ArrayIndexOutOfBoundsException: 0 at org.eclipse.jetty.util.thread.QueuedThreadPool.dump(QueuedThreadPool.java:492) ~[na:na] at org.eclipse.jetty.util.component.AggregateLifeCycle.dump(AggregateLifeCycle.java:241) ~[na:na] at org.eclipse.jetty.server.Server.dump(Server.java:612) ~[na:na] at org.eclipse.jetty.util.component.AggregateLifeCycle.dump(AggregateLifeCycle.java:193) ~[na:na] at org.eclipse.jetty.util.component.AggregateLifeCycle.dump(AggregateLifeCycle.java:184) ~[na:na] at org.eclipse.gyrex.http.jetty.internal.JettyEngineApplication.start(JettyEngineApplication.java:231) ~[na:na] at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) [org.eclipse.equinox.app_1.3.100.v20110214.jar:na] at org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(AnyThreadAppLauncher.java:26) [org.eclipse.equinox.app_1.3.100.v20110214.jar:na] at java.lang.Thread.run(Thread.java:662) [na:1.6.0_24] There is a hard "trace[0]" in that line. I'm still wondering how the stacktrace could be empty, though. Looks like some VM race condition? It isn't critical but a check should do no harm.
(In reply to comment #0) > Looks like some VM race condition? Note, the code has been for this like ages. At least it feels like ages. It only happend just now for the first time ever and I'm unable to reproduce. Really looks like a VM thing.
r2984 Strange??? Put in protection anyway.