[JBoss JIRA] Created: (JBAS-7656) jboss_init_redhat.sh needs to be more robust
by Henrik Aronsen (JIRA)
jboss_init_redhat.sh needs to be more robust
--------------------------------------------
Key: JBAS-7656
URL: https://jira.jboss.org/jira/browse/JBAS-7656
Project: JBoss Application Server
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: Other
Reporter: Henrik Aronsen
Fix For: JBossAS-6.0.0.M2, JBossAS-6.0.0.M3, JBossAS-6.0.0.CR1, JBossAS-6.0.0.GA
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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBAS-8132) Utility to report on differences in domain configuration between domains
by Brian Stansberry (JIRA)
Utility to report on differences in domain configuration between domains
------------------------------------------------------------------------
Key: JBAS-8132
URL: https://jira.jboss.org/browse/JBAS-8132
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: Unscheduled
This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010:
One of the motivations for the domain controller was to help customers manage drift in their JBoss configurations. Because of operational concerns, specifically datacenter isolation, some customers expect to need to run multiple identical domain controllers. They would then still be faced with drift across domain controllers. A utility to detect this drift would be helpful.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years