hey guys. i thought i'd take the webapp that was causing the xsp engine to hang in tomcat-4.0.2 with cocoon-2.0.1 and try it with resin-2.0.3 instead. interesting results...
when i copy the webapp into resin's webapps area while the resin server is still running, it notices the new webapp, initializes and configures it, and everything works fine. cool. however, when i stop and the start resin again, the entire servlet engine hangs after it tries to initialize the c2-based webapp. the last line in resin's error log is: [2002/02/28 02:11:11] DEBUG (2002-02-28) 02:11.11:770 [cocoon ] (Unknown-UR I) Unknown-thread/ThreadSafeComponentHandler: ComponentHandler initialized for: org.apache.avalon.excalibur.component.ExcaliburComponentSelector nothing very interesting or out of the ordinary appears anywhere in that log. nothing shows up in any of the cocoon logs except for the store janitor stuff in the core log: DEBUG (2002-02-28) 02:12.20:621 [core.store-janitor] (Unknown-URI) Unknown-thread/StoreJanitorImpl: JVM total Memory: 4120576 DEBUG (2002-02-28) 02:12.20:621 [core.store-janitor] (Unknown-URI) Unknown-thread/StoreJanitorImpl: JVM free Memory: 1575328 DEBUG (2002-02-28) 02:12.20:621 [core.store-janitor] (Unknown-URI) Unknown-thread/StoreJanitorImpl: Memory is low = false and it does repeat itself periodically, losing 5-10k of free memory each time. access, error, and sitemap logs are all blank. resin won't stop normally, the java processes must be killed. looks like deadlock to me, although why it only happens when the server is being started from scratch is completely beyond me... and of course, frustratingly enough, the c2.0.1 sample webapp works fine, even its xsp pages. does anyone have any suggestions for where i might begin debugging this? - donald --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
