]
Tomaz Cerar closed WFCORE-1388.
-------------------------------
Fix Version/s: 2.0.10.Final
Resolution: Out of Date
I am resolving this as at this point we do have lots of scripts that are battle tested and
work fine.
As such I think this issue is obsolete.
If something is missing somewhere please open new issues for that specific
problem/feature.
jboss_init_redhat.sh needs to be more robust
--------------------------------------------
Key: WFCORE-1388
URL:
https://issues.jboss.org/browse/WFCORE-1388
Project: WildFly Core
Issue Type: Feature Request
Components: Scripts
Reporter: Henrik Aronsen
Fix For: 2.0.10.Final
Attachments: etc_default_jboss.txt, etc_init.d_jboss.txt
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
The init script is currently maintained at
http://code.google.com/p/jboss-rpm/source/browse/#svn/trunk/src/main/etc
(This issue was copied from JBPAPP-3194 as suggested by Fernando Nasser)