Status: Closed (View Workflow)
Affects Version/s: 7.1.0.Final
Fix Version/s: 7.1.1.Final
Git Pull Request:
Similar Issues:Show 10 results
AS7-2514 Deployment name attribute is superfluous AS7-5125 The default-distinct-name can not be set to a "" value, JBAS-014704 is reported AS7-3662 Allow the default configuration file names to be externally set AS7-3475 Properly integrate DMR configuration model with Host Environment and Server Environment AS7-1946 Supported operation names not documented AS7-323 Algorithms for generating server names AS7-4061 CLONE - String configuration parameters for HornetQ address cannot be set via CLI AS7-179 Host model server-config should always have "socket-binding-group-name" and "socket-binding-port-offset" attributes AS7-3960 Unable to set datasource attribute flush-strategy via CLI AS7-4436 setting debug-enabled and debug-options via dmr does not work
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
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.