In JBoss 3.2.1, access to the JMX console results in an attempted write to the JBoss /bin directory. The default permissions are root-writeable only so JMX console access fails. Files are of the form filesN where N is arbitrary AFAI can tell. Fixed by making /bin writeable by jboss group but JBoss should really use another directory for compilation workfiles. Reproducible: Always Steps to Reproduce: 1. groupadd and useradd 'jboss' 2. emerge /usr/portage/net-www/jboss/jboss-3.2.1.ebuild 3. /etc/init.d/jboss start 4. from browser, access http://host:8080/jmx-console Actual Results: HTTP error 500 server.log shows exception compiling jsp for jmx console with problem related to /opt/jboss-3.2.1/bin/filesN access (N is some number) Expected Results: Displayed the JMX console
Created attachment 13382 [details, diff] A patch to the jboss 3.2.1 init.d/jboss script I tried a few different approaches (TMPDIR, java.io.tmpdir), but this one seemed to work and the others did not. I hope this helps other people as well.
Created attachment 13384 [details, diff] A patch to the jboss 3.2.1 init.d/jboss script I tried a few different approaches (TMPDIR, java.io.tmpdir), but this one seemed to work and the others did not. I hope this helps other people as well.
OK, this is getting moved to mkennedy. Since 3.2.1 did not follow the setup in 3.0.6, I have no idea what's going on with this package anymore.
Created attachment 14120 [details, diff] A patch against /usr/portage/net-www/jboss/files/3.2.1 This should be applied against the conf.d/jboss and init.d/jboss files that exist in /usr/portage/net-www/jboss/files/3.2.1. This patch allows the init.d/jboss script to both start and stop jboss from either a login shell (as root of course) or at system boot and shutdown. The problem with the old version of the scripts was that they assumed a valid environment existed - and this is not the case at system boot and shutdown.
Created attachment 14121 [details, diff] A patch against /usr/portage/net-www/jboss/files/3.2.1 This should be applied against the conf.d/jboss and init.d/jboss files that exist in /usr/portage/net-www/jboss/files/3.2.1. This patch allows the init.d/jboss script to both start and stop jboss from either a login shell (as root of course) or at system boot and shutdown. The problem with the old version of the scripts was that they assumed a valid environment existed - and this is not the case at system boot and shutdown.
please check that jboss-3.2.1-r1 corrects this bug
no input, assuming this can be closed
