Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-6956

Wrong endpoint-name if the JBoss server name and 'jboss.node.name' are both provided to the server

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 26.0.0.Beta3, 26.0.0.Final
    • 25.0.0.Final
    • Server
    • None
    • Hide

      Configure the server with the server name set in the configuration (standalone.xml) like:

      <?xml version="1.0" encoding="UTF-8"?>

<server xmlns="urn:jboss:domain:20.0" name="custom-server-name">
    <extensions>
        <extension module="org.jboss.as.clustering.infinispan"/>
        ...

      Then start the server with:
      $JBOSS_HOME/bin/standalone.sh -Djboss.node.name=custom-jboss-node-name

      The server.log then shows:

      2024-08-21 14:20:29,309 INFO  [org.jboss.modules] (main) JBoss Modules version 2.1.5.Final
2024-08-21 14:20:29,592 INFO  [org.jboss.msc] (main) JBoss MSC version 1.5.5.Final
2024-08-21 14:20:29,599 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
2024-08-21 14:20:29,665 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly 33.0.0.Final (WildFly Core 25.0.0.Final) starting
2024-08-21 14:20:29,666 DEBUG [org.jboss.as.config] (MSC service thread 1-1) Configured system properties:
        [Standalone] = 
        ...
        jboss.node.name = custom-jboss-node-name
        ...
        jboss.server.name = p1
        ...
...

      If getting those values via CLI once the server is started, the result is:

      $JBOSS_HOME/bin/jboss-cli.sh -c --command="/core-service=platform-mbean/type=runtime:read-attribute(name=system-properties)" | grep -E "jboss.node.name|jboss.server.name"

              "jboss.node.name" => "custom-server-name",
        "jboss.server.name" => "custom-server-name",
      Show
      Configure the server with the server name set in the configuration ( standalone.xml ) like: <?xml version= "1.0" encoding= "UTF-8" ?> <server xmlns= "urn:jboss:domain:20.0" name= "custom-server-name" > <extensions> <extension module= "org.jboss.as.clustering.infinispan" /> ... Then start the server with: $JBOSS_HOME/bin/standalone.sh -Djboss.node.name=custom-jboss-node-name The server.log then shows: 2024-08-21 14:20:29,309 INFO [org.jboss.modules] (main) JBoss Modules version 2.1.5.Final 2024-08-21 14:20:29,592 INFO [org.jboss.msc] (main) JBoss MSC version 1.5.5.Final 2024-08-21 14:20:29,599 INFO [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final 2024-08-21 14:20:29,665 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly 33.0.0.Final (WildFly Core 25.0.0.Final) starting 2024-08-21 14:20:29,666 DEBUG [org.jboss.as.config] (MSC service thread 1-1) Configured system properties: [Standalone] = ... jboss.node.name = custom-jboss-node-name ... jboss.server.name = p1 ... ... If getting those values via CLI once the server is started, the result is: $JBOSS_HOME/bin/jboss-cli.sh -c --command="/core-service=platform-mbean/type=runtime:read-attribute(name=system-properties)" | grep -E "jboss.node.name|jboss.server.name" "jboss.node.name" => "custom-server-name", "jboss.server.name" => "custom-server-name",

      If WildFly is started with the server name set in the server configuration (<server ... name="custom-server-name">) and the jboss.node.name set, the jboss.node.name is getting replaced during the server start with the value of the server name.

              rhn-support-jbaesner Joerg Baesner
              rhn-support-jbaesner Joerg Baesner
              Richard Achmatowicz
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: