[jboss-jira] [JBoss JIRA] (AS7-348) By default use a common identifier anywhere a server "id" notion is exposed in the configuration
David Lloyd (Commented) (JIRA)
jira-events at lists.jboss.org
Wed Nov 9 21:12:45 EST 2011
[ https://issues.jboss.org/browse/AS7-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641610#comment-12641610 ]
David Lloyd commented on AS7-348:
---------------------------------
We're using ${jboss.node.name} as the default node name for a server. In each component using this name, they can provide an overridden name instead.
${jboss.node.name} is derived from ${jboss.host.name} by default (unless overridden), and ${jboss.host.name} is derived from ${jboss.qualified.host.name}. The ${jboss.qualified.host.name} is derived from the system hostname (or computer name, for Windows) environment variable (if any), or failing that, the local host's network IP address.
> By default use a common identifier anywhere a server "id" notion is exposed in the configuration
> ------------------------------------------------------------------------------------------------
>
> Key: AS7-348
> URL: https://issues.jboss.org/browse/AS7-348
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: David Lloyd
> Fix For: 7.1.0.CR1
>
>
> This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010:
> >> * JBoss Transactions, jvm-route, jboss messaging all require a
> >> unique identifier for them to behave properly in a clustered
> >> environment. I would like one unique identifier for each server
> >> configuration and for all services that need a unique identifier
> >> to reference it by default. Then I don't have to worry about
> >> unique identifiers when creating new servers.
> (The jboss messaging bit is out of date with respect to AS 7, which will use HornetQ and thus has no ServerPeerId configuration required. But the basic point is spot-on.)
--
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
More information about the jboss-jira
mailing list