[
https://issues.jboss.org/browse/AS7-4110?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-4110:
---------------------------------------
The linked pull request should clean up any issues related to the handling of
jboss.node.name within the server. If you can check if it solves the particular issues you
were experiencing that would be great.
The node name can not set proper via <server name=> attribute
-------------------------------------------------------------
Key: AS7-4110
URL:
https://issues.jboss.org/browse/AS7-4110
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB, Remoting, Server, Transactions
Affects Versions: 7.1.0.Final
Reporter: Wolf-Dieter Fink
Assignee: Brian Stansberry
Fix For: 7.1.1.Final
The node name can be set by using '-Djboss.node.name' in standalone mode.
In domain mode this is not possible.
The attribute "name" of the server element should be used for that (for SA and
domains host.xml)
But current there is no effect if the client use EJBClient.getUserTransaction( node-name
), client error is "No EJBReceiver available for node name
MyNode".
The management console shows the correct server name set by <server name=>.
Also if the system-properties element is used to set "jboss.node.name" this is
not reflected by management console
but if an application use System.getProperty("jboss.node.name") the value of
the system-property is returned.
--
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