[JBoss JIRA] Created: (JBAS-8208) Expressing configuration property metadata in domain schema
by Brian Stansberry (JIRA)
Expressing configuration property metadata in domain schema
-----------------------------------------------------------
Key: JBAS-8208
URL: https://jira.jboss.org/browse/JBAS-8208
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Emanuel Muckenhuber
Fix For: 7.0.0.M1
Clients of the domain management API are going to need to see metadata about the various items they are configuring. Besides simple type stuff, information on things like whether changes require restart, etc, need to be available.
This task is to determine where this information comes from and how it can be made available to the layer that provides it to the client.
--
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
14 years, 6 months
[JBoss JIRA] Created: (JBAS-8137) Simple start and stop scripts
by Brian Stansberry (JIRA)
Simple start and stop scripts
-----------------------------
Key: JBAS-8137
URL: https://jira.jboss.org/browse/JBAS-8137
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:
>> I would like to see all the configurations that normally get set on the
>> command line (JBoss opts and system props) moved to a config file so all
>> that is ever required to start a Jboss instance is simply "run.sh
>> /<configuration>/".
The domain and host configuration files we'll introduce with AS 7 should encapsulate most things that are currently passed in via -D or the arguments to main(). If we start adding additional command line options that need to be processed before the domain/host configuration files are read, we should make it easy to set those in a configuration file (perhaps a simple properties file).
--
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
14 years, 6 months
[JBoss JIRA] Created: (JBAS-8744) Failure to start the JVM should trigger a management update plan to rollback
by Andrig Miller (JIRA)
Failure to start the JVM should trigger a management update plan to rollback
----------------------------------------------------------------------------
Key: JBAS-8744
URL: https://issues.jboss.org/browse/JBAS-8744
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Domain Management
Affects Versions: 7.0.0.Alpha1
Reporter: Andrig Miller
Assignee: Brian Stansberry
Fix For: 7.0.0.Beta1
I have come across situations where certain JVM options, typically related to NUMA options, can cause the JVM to segfault. With our domain model, we expose the ability to set the JVM options, so I think this certainly would be a possibility.
So, as we discussed on the Andiamo call today, this type of situation should cause a rollback of the management update plan, if the JVM fails to start.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[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
14 years, 6 months
[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
14 years, 6 months