|
From: pgruber <pau...@gm...> - 2007-09-25 01:31:04
|
Apologize this is a cross post from the terracotta forum, but the more I look the more I think perhaps the solution is more on the Jetty side then the terracotta side: Here is what I did Follow directions on the jetty integration (moved the config from the contextdeployer.xml to the jetty-web.xml as it is within JBoss, maybe this is the problem?) Fixed various missing boot.jar Start Terracotta on local machine Start JBoss Jetty on local machine log in to my application kill jboss/jetty start jboss/jetty refresh my browser window (same one from before so should be same session). JBoss/Jetty is completly frozen, I get nothing in any log anywhere, CPU is not being used, just dead. Everything looks good in the admin console again after restart (one client, and roots). I then tried this with 2 apps running at the same time on a single machine and got the same results. My app will not work again untill I shut down the terracotta server and the app server and restart them both. My guess is there is somthing wrong with the locking...but don't know where to go from there. I recieved some advice to disable the lock in the terracotta config file (change to concurrent). This allowed the server to come back but then I started getting class not found errors in the terracotta config. The classes are all in the webapp, but I am thinking perhaps it has to do with JBoss doing the deployment maybe there is somthing with the classloader that is different. I am happy to poke around in the Jetty code, but would need some help in where to start looking. The terracotta thread and config file can be found at: http://forums.terracotta.org/forums/posts/list/488.page Any help is greatly apreciated. -- View this message in context: http://www.nabble.com/jboss-jetty-cluster-freezes-tf4512816.html#a12871606 Sent from the Jetty Support mailing list archive at Nabble.com. |