[JBoss JIRA] (AS7-2410) Specify Domain Controller arg to bin/domain.sh
by Rich Sharples (Created) (JIRA)
Specify Domain Controller arg to bin/domain.sh
----------------------------------------------
Key: AS7-2410
URL: https://issues.jboss.org/browse/AS7-2410
Project: Application Server 7
Issue Type: Enhancement
Components: Domain Management
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Brian Stansberry
Fix For: 7.1.0.Beta1
When I start a server as part of a remote domain I currently have to specify the remote DC in host.xml :
<domain-controller>
<!-- <local/> -->
<!-- Alternative remote domain controller configuration with a host and port -->
<remote host="192.168.1.3" port="9999"/>
</domain-controller>
would be much more convenient to specify this as a property and be able to specify it on the command line - that way I don't have to touch host.xml. With a large server group / domain that would be a real time-saver.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBAS-9097) Management only standalone mode
by Brian Stansberry (JIRA)
Management only standalone mode
-------------------------------
Key: JBAS-9097
URL: https://issues.jboss.org/browse/JBAS-9097
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.0.0.Beta4
See parent task for core concept.
In standalone mode, the issue is distinguishing operations that provide management services from those that don't. If the server is started in "management only" mode a RuntimeContext should only be provided to handlers for those operations.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (AS7-1642) If --domain-config is used in domain.sh, changes to the configuration using the web console are not correctly persisted
by Georges Berscheid (JIRA)
If --domain-config is used in domain.sh, changes to the configuration using the web console are not correctly persisted
-----------------------------------------------------------------------------------------------------------------------
Key: AS7-1642
URL: https://issues.jboss.org/browse/AS7-1642
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.1.Final
Environment: RHEL6
Reporter: Georges Berscheid
Assignee: Brian Stansberry
When AS7 is started using $JBOSS_HOME/bin/domain.sh --domain-config=/etc/as7/domain.xml, all changes made through the web console are persisted in $JBOSS_HOME/domain/configuration/domain.xml.
That means for example that deployments don't survive server restarts. Also trying to add the same deployment again does not seem to work, probably because the files already exist in the $JBOSS_HOME/domain/content directory.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (AS7-1994) access to the ModelNodeRegistration during handling of an operation and during deployment
by Stefano Maestri (JIRA)
access to the ModelNodeRegistration during handling of an operation and during deployment
-----------------------------------------------------------------------------------------
Key: AS7-1994
URL: https://issues.jboss.org/browse/AS7-1994
Project: Application Server 7
Issue Type: Task
Affects Versions: 7.1.0.Alpha1
Reporter: Stefano Maestri
Assignee: Brian Stansberry
Fix For: 7.1.0.CR1
Hi All,
I'm trying to resume here the discussion I had yesterday on IRC with
Brian and Jesper.
Basically JCA needs to have and already deployed instance of
ResourceAdapter when adding its metrics and some operation. The reason
for that is because some operation and metrics availability are known
only at runtime, depending from RA status and/or vendor specific feature
known only.
Speaking from a Model point of view the basically issue is to have
access to the ModelNodeRegistration when the RA instance is created and
these runtime infos are available. There are 2 cases:
1) during handling ADD operation for a DataSource or special
ResourceAdapter creation withour rar deployment (like hornetQ).
2) during foo.rar deployment chain
We have also discussed where we can put these operation in the model
tree. Also in this case there are two possible places:
1) at subsystem level for special no-deployment RA (DataSources and
HornetQ atm). So we will obtain something like
/subsystem=datasource/data-source=myDS and /subsystem=hq/ra
2) at DUP level /deployment=foo.rar Having this deployment support we
can remove the current operation in /subsystem=resource-adapters that is
redudant, referring the same RA (or better a subset of deployed ones)
Hoping to have written all the matters discussed, feel free to integrate
and/or ask.
regards
S.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months