Application Server 7
  1. Application Server 7
  2. AS7-4110

The node name can not set proper via <server name=> attribute

    Details

    • Similar Issues:
      Show 10 results 

      Description

      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.

        Issue Links

          Activity

          Hide
          David Lloyd
          added a comment -

          Assigning to Brian since he foolishly volunteered to look into this.

          Show
          David Lloyd
          added a comment - Assigning to Brian since he foolishly volunteered to look into this.
          Hide
          Brian Stansberry
          added a comment -

          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.

          Show
          Brian Stansberry
          added a comment - 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.
          Hide
          Jitka Kozana
          added a comment -

          verified: issue present in EAP 6.0.0.ER3, issue fixed in EAP 6.0.0.CR1

          Show
          Jitka Kozana
          added a comment - verified: issue present in EAP 6.0.0.ER3, issue fixed in EAP 6.0.0.CR1

            People

            • Assignee:
              Brian Stansberry
              Reporter:
              Wolf-Dieter Fink
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: