Uploaded image for project: 'JBoss Enterprise Application Platform 6'
  1. JBoss Enterprise Application Platform 6
  2. JBPAPP6-484

mod_cluster does not generate UUID automatically

    XMLWordPrintable

    Details

    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      As a workaround, you have to set instance-id. Worker node will be distinguishable from the others then and balancer operates normally.

      e.g.

      <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="false" instance-id="hellnode01">
      
      Show
      As a workaround, you have to set instance-id . Worker node will be distinguishable from the others then and balancer operates normally. e.g. <subsystem xmlns= "urn:jboss:domain:web:1.1" default-virtual-server= "default-host" native= "false" instance-id= "hellnode01" >

      Description

      According to the documentation, mod_cluster should generate its own UUID automatically.

      It does not with EAP 6 ER3.

      The result of this behaviour is "Unidentified node" messages on Mod_cluster manager console and "Can't read MEM" messages in balancer log. It is clear, that balancer is unable to distinguish between nodes and hence goes crazy.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                ctomc Toma┼ż Cerar
                Reporter:
                mbabacek Michal Karm
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: