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,
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 cluster instances are located in the same physical server.
D:\glassfish4\glassfish\bin>asadmin create-node-config --help
create-node-config(1) asadmin Utility Subcommands create-node-config(1)
create-node-config - creates a node that is not enabled for remote
[--installdir as-install-parent] [--nodedir node-dir] node-name
The create-node-config subcommand creates a node that is not enabled
for remote communication. The create-node-config subcommand does not
require the Distributed Component Object Model (DCOM) remote protocol
or secure shell (SSH) to be configured to create the node.
A node represents a host on which the GlassFish Server software is
installed. A node must exist for every host on which GlassFish Server
| To represent the host where
| the DAS is running,
| GlassFish Server provides
| the predefined node
| localhost-domain. The
| predefined node
| localhost-domain is not
| enabled for remote
All administration of instances on a node that is not enabled for
remote communication must be performed on the host that the node
represents. The domain administration server (DAS) on a remote host
cannot contact the node. To administer instances on a node that
represents a host that is remote from the DAS, you must use the
However, you may use stop-local-instance(1) or stop-instance(1) to stop
This subcommand is supported in remote mode only.
The name of the host that the node represents. If this option is
omitted, no host is specified for the node.