Hei, As one of the persons to have reported the deadlock problem with log4j logging in jboss (bug 623223), I have been following the problem and was happy to see that it was fixed in cvs. Regarding releases, JBoss 3.0.4 contains the fix but there has been no release of JBoss 2.4.x containing the fix. As we haven't started migration to JBoss 3.0, we need to either get a release of JBoss 2.4.x or patch jboss to solve the problem.
I was ready for the former, but I was confused by the fact that the changes to the fixes are different between the JBoss 2.4.x and 3.0.X branches. In branch 2.4.X, two patches were applied to 'better fix the problem' using a ThreadLocal instance instead of synchronized blocks. Those changes were not applied on 3.0.X. I am trying to understand if this is a mistake or not. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jboss/src/main/org/jboss/logging/log4j/Attic/CategoryStream.java http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jboss-common/src/main/org/jboss/logging/util/CategoryStream.java If somebody can point me out if I can safely apply all the changes in CategoryStream on top of a clean 2.4.7 JBoss with Jetty installation so that this bug doesn't happen anymore. Last question: is there any release planned for the 2.4.X branch. There has been a number of interesting fixes on that branch (tomcat security fixes, deadlock, etc...), so would soon a good idea to all the users who haven't had the time to upgrade. Cheers, Jerome ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
