[jboss-user] [Remoting] - Re: JBoss Remoting & JDK 6.0 situation deadlock

tom.elrod@jboss.com do-not-reply at jboss.com
Fri Jan 12 14:28:11 EST 2007

(Per http://jira.jboss.com/jira/browse/JBREM-659)

Have update all the places where ClassLoader.loadClass() was being called and either replaced with Class.forName() call or changed to use the ClassLoaderUtility class. These changes have been made to HEAD, remoting_2_x and remoting_1_4 branches.

Have also created a 1.4.6.GA release for these changes (with tag of remoting_1_4_6_GA) and have published to jboss repository (see Jhttp://repository.jboss.com/jboss/remoting/1.4.6.GA/lib/)

Although was able to manually test some of the remoting tests within the testsuite using jdk 1.6, could not run the automated testsuite run with jdk 1.6. The reason for this is that distributed test framework used (JBoss JRunit) uses JGroups for its communication transport, which itself uses ClassLoader.loadClass() and therefore can't run under jdk 1.6 (see http://javagroups.cvs.sourceforge.net/javagroups/JGroups/src/org/jgroups/util/Util.java?revision=1.113&view=markup).

Therefore, although 1.4.6.GA, 2.2.0.Beta1 and any 3.x releases *should* work with jdk 1.6, I can't say they will with certainty since can't run the full testsuite.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001080#4001080

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001080

More information about the jboss-user mailing list