ports/58743: Update java/jboss3 to JBoss 3.2.2

[Stephen Forbes]

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

From: Stephen Forbes <forbes at inditech.com>
To: freebsd-gnats-submit at FreeBSD.org, jonc at chen.org.nz
Cc: des at des.no, jon at freebsd.org
Subject: Re: ports/58743: Update java/jboss3 to JBoss 3.2.2
Date: Wed, 26 Nov 2003 01:29:20 +0000

 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.modelm=
 bean.ModelMBeanInvoker: field ALL_DESCRIPTORS not f
 ound
         at javax.management.MBeanServerFactory.createMBeanServer(MBeanServe=
 rFactory.java:180)
         at javax.management.MBeanServerFactory.createMBeanServer(MBeanServe=
 rFactory.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)
 >>>>>>>>>>>>>>
 
 This could be due to the problem cited in http://www.freebsd.org/cgi/query-=
 pr.cgi?pr=3D58743
 
 This page raises several issues:
 
 1) This problem is known about, I read "While I'm here, fix problem of =
 JBoss not starting up once installed due to ownership/permission problems."=
  But this problem for me is still in effect. I really appreciate the hard =
 work that goes into FreeBSD, but I've waited a month now for this problem =
 to be resolved via the ports tree, and I'm still waiting.
 
 2) I read that "Severity" is "non-critical", JBoss3 not booting is severe =
 for me.
 
 3) I read that the "State" is "closed", it doesn't appear closed as the =
 problem hasn't been cleared in the current version in the posts tree. =
 jonc at chen.org.nz states that " I don't mind taking over the port, but =
 please note that I am *NOT* jon at freebsd.org, and I do not have commit =
 privileges." So, does this mean that jonc at chen.org.nz has solved the =
 problem with JBoss 3 not starting but that it can't be updated to the =
 ports tree ? If so then how can the state be closed. Or maybe I'm =
 experiencing a different problem ?
 
 4) Tantalisingly the fix is provided as a diff output. The problem is that =
 I don't know what to do with this output and that there are no instructions=
  to that effect. So, it's not really a fix, not for me anyway.
 
 >>>>>>>>>>>>>>
 diff -ru ./Makefile /home/jonc/ports/jboss3/Makefile
 --- ./Makefile	Tue Jul 15 09:35:47 2003
 +++ /home/jonc/ports/jboss3/Makefile	Fri Oct 31 09:16:47 2003
 @@ -6,8 +6,7 @@
  #
  PORTNAME=3D	${APP_TITLE:L}
 -PORTVERSION=3D 	3.2.1
 -PORTREVISION=3D	1
 +PORTVERSION=3D 	3.2.2
  CATEGORIES=3D	java
 <snip>
 >>>>>>>>>>>>>>
 
 5) I read that this fix has been committed, yet, for me, there is still a =
 problem. Could it be that the fix is incorrect or that there was a problem =
 with committing ?
 
 >>>>>>>>>>>>>>
 State-Changed-From-To: open->closed=20
 State-Changed-By: glewis=20
 State-Changed-When: Tue Nov 4 09:57:28 PST 2003=20
 State-Changed-Why: =20
 Committed, thanks!=20
 >>>>>>>>>>>>>>
 
 Can you tell me how to apply this fix or, even better, when this issue =
 will be sorted and committed in the ports collection ?
 
 Many thanks for all your hard work,
 
 Please help,
 
 Steve