-
1. Re: Running JBoss with Java 6 (JDK 6)
agustinbelmonte Jan 17, 2007 7:18 AM (in response to felderr)Hello,
i think there is no problem running on java 6 because jboss is j2ee certified with java 1.4 and later versions. -
2. Re: Running JBoss with Java 6 (JDK 6)
dwin Jan 17, 2007 2:14 PM (in response to felderr)In my experience, JBoss does not running correctly with JDK 6. I've heard several issues, especially when using JBoss web services.
Until there is an official release and assurance that JBoss 4.x or even JBoss 5.x will comply with Java 6..
Eventually, I am guessing that they will modify and address the bugs that occur with Java 6 and JBoss AS. Not sure when, but I m guessing soon. -
3. Re: Running JBoss with Java 6 (JDK 6)
felderr Apr 13, 2007 10:56 AM (in response to felderr)JBoss 4.0.5 works fine with Java 6!
Just tried to run JBoss 5.0.0 beta 2 with Java 6 and failed:
java.lang.IllegalStateException: Class not found: [Ljava.lang.String;
The server does not come up as it runs into the following bug within JDK 1.6.0:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6434149
Any workarounds planned by JBoss? -
4. Re: Running JBoss with Java 6 (JDK 6)
tthunt Apr 16, 2007 10:54 AM (in response to felderr)FelderR,
I've been able to get Web Services wtih annotations to deploy using JBoss 4.0.5 with Java 6, but when the test client tries to connect, I was getting errors due to a Logging class not being found in the CLASSPATH. Have you seen this?
Thanks,
TTH -
5. Re: Running JBoss with Java 6 (JDK 6)
nartf Apr 26, 2007 3:59 AM (in response to felderr)Hi
I encountered the exception below running JBoss 4.0.3SP1 on JDK6. The exception was thrown in an application that hadn't been throwing that exception on JDK1.4.
Interesting: The first occurrence of the exception takes place after a seemingly random amount of time after launch (0 - 60 min). Once it has been thrown, it won't stop being thrown.
Has anyone experienced similar things?
10:10:00,187 SEVERE [EJobEngine] Error sending JMS message; job is NOT run
javax.jms.JMSSecurityException: User: null is NOT authenticated
at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:215)
at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:51)
at org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:734)
at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:287)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:204)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManagerjava:369)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Thread.java:619) -
6. Re: Running JBoss with Java 6 (JDK 6)
alexg79 Apr 26, 2007 9:11 AM (in response to felderr)"FelderR" wrote:
JBoss 4.0.5 works fine with Java 6!
Just tried to run JBoss 5.0.0 beta 2 with Java 6 and failed:
java.lang.IllegalStateException: Class not found: [Ljava.lang.String;
The server does not come up as it runs into the following bug within JDK 1.6.0:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6434149
Any workarounds planned by JBoss?
This has been extensively discussed on the EJB 3 forum. It is not a bug in JDK 6, but a bug in several parts of the JBoss AS. The problem stems from the improper use of classloaders -- classes should be loaded with Class.forName(name), not obj.class.getClassLoader().loadClass(name). The latter method worked up until JDK 6 due to an unintended side effect of the class loading mechanism. This has already been fixed in JBoss Remoting, but apparently not in other programs. -
7. Re: Running JBoss with Java 6 (JDK 6)
pedalshoe Nov 13, 2007 12:19 AM (in response to felderr)Are there any plans to fix this in JBossAS? Please fix it.
Seems like code in GlasFish was already corrected:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=714
Thank You