ports/58743: Update java/jboss3 to JBoss 3.2.2

[Jonathan Chen]

The following reply was made to PR ports/58743; it has been noted by GNATS.

From: Jonathan Chen <jonc at chen.org.nz>
To: Stephen Forbes <forbes at inditech.com>
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: ports/58743: Update java/jboss3 to JBoss 3.2.2
Date: Wed, 26 Nov 2003 15:28:53 +1300

 On Wed, Nov 26, 2003 at 01:29:20AM +0000, Stephen Forbes wrote:
 > Hello,
 > 
 > Since FreeBSD 4.9-RELEASE came out a month ago, I've been repeatedly refreshing my ports tree and trying to install /usr/ports/java/jboss3 , currently jboss-3.2.2,  from the ports tree into a clean install of 4.9. The problem is that when I try to subsequently boot JBoss, it fails and I get the following messages in /usr/local/jboss3.2/log/stderr.log :
 > 
 > >>>>>>>>>>>>>>
 > Failed to boot JBoss:
 > java.lang.RuntimeException: Unable to create the MBean server instance. Class org.jboss.mx.server.MBeanServerImpl has raised a
 > n exception in constructor: java.lang.NoSuchFieldError: org.jboss.mx.modelmbean.ModelMBeanInvoker: field ALL_DESCRIPTORS not f
 > ound
 >         at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:180)
 >         at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:80)
 >         at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:327)
 >         at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
 >         at org.jboss.Main.boot(Main.java:150)
 >         at org.jboss.Main$1.run(Main.java:395)
 >         at java.lang.Thread.run(Thread.java:484)
 > >>>>>>>>>>>>>>
 
 The problem I fixed with the ownership permissions is not the problem
 you're experiencing.
 
 Let me guess: You're running JDK1.3.1 (or thereabouts). The JBoss-forums
 have had a discussion about this, and they have speculated that there
 is some binary incompatiblity with the java-classes between JDK1.4+
 and JDK1.3.1. Basically, they've compiled the JBoss binaries with
 JDK1.4+, and it doesn't work with anything less.
 
 Solutions that have been proposed:
     1. build JBoss with JDK1.3.1 (JBoss isn't doing this, we may have
        to do a local build)
     2. upgrade to JDK1.4.2.
 
 I haven't had time to do Solution 1, would it be possible for you to
 try solution 2?
 -- 
 Jonathan Chen <jonc at chen.org.nz>
 ----------------------------------------------------------------------
                              "Beer. Now there's a temporary solution."
                                                        - Homer Simpson