2013/1/21 Rainer Jung <rainer.j...@kippdata.de>: > I did another run for "ant test" for 7.0.35 and when using APR I got the > following error the first time (never saw that before): > > (...) > [junit] INFO: Stopping ProtocolHandler > ["http-apr-127.0.0.1-auto-2-42652"] > [junit] Jan 18, 2013 4:37:59 PM > org.apache.tomcat.util.net.AprEndpoint$Poller doPoll > [junit] SEVERE: Critical poller failure (restarting poller): [9] Bad > file number > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > OS is Solaris 10, using Java 1.6.0_37. > > The ant and Tomcat processes are still there to investigate, Tomcat is > looping on CPU in Thread 26. Stack is: > (...) >
Well, it happens only during shutdown, so it might be that it is not so important... What is the downside here -- Tomcat hangs due to an infinite loop? If so then it is not good. I wonder why that log message says "restarting poller". Does it try to start the poller when everything else shuts down? > This is an indication for a synchronization problem in the code using > the pool. I wonder whether some test case has higher chance of triggering this. The test case where it happened is "org.apache.jasper.compiler.TestParser" ? Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
