-
Patch
-
Resolution: Obsolete
-
Major
-
4.3.0.GA, EAP 5.0.0
-
None
-
Linux, RHEL5
-
Not Required
I have tried to address the shortcomings of the current JBoss init script for RHEL5:
- Uses PID file
- Supports chkconfig
- Supports start, stop, force-stop, reload, force-reload, status
- Supports custom user and password on shutdown
- Supports custom jndi host/port on shutdown
- Does not allow second instance to start when one is already running
- Does not rely on other files such as run.sh and run.conf
- Verifies successful startup
- The init script does not have to be edited, use the standard location for configuration (/etc/default/jboss) instead
- Runs out of the box when no configuration is provided
- Should support most Linuces
All feedback is welcome – I'm sure I forgot something in the provided script.
- is related to
-
JBPAPP-2381 add chkconfig support to jboss_init_redhat.sh
- Resolved
-
JBPAPP-1429 scripts in server bin directory issues
- Closed
-
JBPAPP-2868 run.sh script disables IPv6 on Linux
- Closed
-
JBPAPP-3029 jboss_init_redhat script stop feature generates exception
- Closed
-
JBAS-5225 status function must return non-zero when jbossas is not running
- Closed
-
JBAS-4107 New init script for Red Hat Enterprise Linux (and variants)
- Closed
-
JBAS-5489 JBOSSSH and JBOSS_CMD_START confused in jboss_init_redhat.sh
- Closed
- relates to
-
WFCORE-1388 jboss_init_redhat.sh needs to be more robust
- Closed
-
JBPAPP-3266 No instructions on running as a service on Linux
- Closed
-
JBPAPP-2488 RPM distribution for the EAP 5
- Closed