Details

    • Type: Sub-task Sub-task
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.1
    • Component/s: jms
    • Labels:
      None

      Description

      When configuring glassfish jms cluster with master broker in EMBEDDED or LOCAL mode, glassfish jms module will generate properties of 'imq.cluster.brokerlist' and 'imq.cluster.masterbroker' and passes those to MQ for bootstrap. For example,

      imq.cluster.brokerlist=mq://host2:3076/,mq://host1:2076/
      imq.cluster.masterbroker=mq://host1:2076/

      The hostnames used in the properties are got from glassfish cluster nodes on which the glassfish instances reside. So at any time, please use unique hostnames which can be resolved at any physical servers on the network. Don't use localhost except that all the glassfish cluster instances are located in the same physical server.

        Activity

        Hide
        amyk added a comment -

        A loopback IP address on one system can't be used as the 'address' of the system to other systems for communication.

        You should be able to use a non loopback IP address and different ports to form a cluster on same system.

        Show
        amyk added a comment - A loopback IP address on one system can't be used as the 'address' of the system to other systems for communication. You should be able to use a non loopback IP address and different ports to form a cluster on same system.
        Hide
        dmatej added a comment -

        Once more again: then Glassfish fails to start, because IP address is changed every time I move to another network. Better approach is to let the configuration on the administrator - you can warn him about that, but you should allow that. I don't know about any other system which is so restrictive (and limited).

        Show
        dmatej added a comment - Once more again: then Glassfish fails to start, because IP address is changed every time I move to another network. Better approach is to let the configuration on the administrator - you can warn him about that, but you should allow that. I don't know about any other system which is so restrictive (and limited).
        Hide
        amyk added a comment - - edited

        Please file a jira to GlassFish server or GlassFish server JMS module to get real hostnames or real IP addresses of the GlassFish server instances when compose the GlassFish MQ cluster configuration properties

        Show
        amyk added a comment - - edited Please file a jira to GlassFish server or GlassFish server JMS module to get real hostnames or real IP addresses of the GlassFish server instances when compose the GlassFish MQ cluster configuration properties
        Hide
        dmatej added a comment -

        That issue already exists, but does not resolve the problem - there is no fixed hostname on notebook except the one resolved to loopback IP adress. All other names depend on a network DNS+DHCP. This is why I am writing it here and not to another issue or forum.

        Show
        dmatej added a comment - That issue already exists, but does not resolve the problem - there is no fixed hostname on notebook except the one resolved to loopback IP adress. All other names depend on a network DNS+DHCP. This is why I am writing it here and not to another issue or forum.
        Hide
        amyk added a comment - - edited

        It's the runtime hostname/IP addresses needed - not statically configured. The RE of GLASSFISH-17278 has determined it as a doc issue that how it currently works. You can reopen GLASSFISH-17278 or file a separate RFE jira so that it will go to the right responsible engineer. This jira sub-task is currently assigned to tech. writer.

        Show
        amyk added a comment - - edited It's the runtime hostname/IP addresses needed - not statically configured. The RE of GLASSFISH-17278 has determined it as a doc issue that how it currently works. You can reopen GLASSFISH-17278 or file a separate RFE jira so that it will go to the right responsible engineer. This jira sub-task is currently assigned to tech. writer.

          People

          • Assignee:
            Mike Fitch
            Reporter:
            David Zhao
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: