On Fri, 29 Aug 2003, Bruno Dumon wrote: > For me it works with Linux/Sun jdk 1.4.2, it doesn't work with 1.3.1. > For Carsten it doesn't work with Windows/jdk 1.4 either. I've done all > my testing with the Jetty which ships with Cocoon. > > I've added some println's here and there and it appears that, with > 1.3.1, the CommandManager starts working but stops as soon as Jetty > prints out the following lines: > Fri Aug 29 13:58:07 CEST 2003 Listening for connections ... > 13:58:07.575 EVENT Started SocketListener on 0.0.0.0:8888
I have the above also in with sun jdk 1.4.2 on Linux. > It seems that the thread that was executing the commands is somehow not > released (or whathever), so when the ThreadManager wants to execute the > next command it keeps waiting for a thread to be released (this waiting > happens in Doug Lea's Executor). If the "threads-per-processor" > parameter is augmented to "2", then it keeps working. Have not tried using a second Thread. > > According to Giacomo, the CommandManager works just fine in a > non-servlet environment. Right. -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
