Bypassing the port-mapper for clustering and JMS TCP connections
1) Bypassing port mapper for clustering:
I modified the contents of my cluster.properties file to this:
imq.cluster.brokerlist=192.168.0.75:40870,192.168.0.188:40870
I also added the following property in config.properties for the broker instance ( /opt/sun/mq/var/instances/imqbroker/props/config.properties
):
imq.cluster.port=40870
I then stopped all brokers ( 2 ) on the cluster ( test environment ), made sure iptables allow port 40870, and started all brokers.
The output of imqcmd query bkr -u admin
on both brokers show the following ( notice the active and configured brokerlist ):
Cluster ID
Cluster is Highly Availablefalse
Cluster Broker List (active) mq://192.168.0.188:7676/
Cluster Broker List (configured) mq://192.168.0.75:40870/,mq://192.168.0.188:40870/
Cluster Master Broker
Cluster URLfile:///opt/sun/mq/var/instances/imqbroker/props/cluster.properties
Furthermore, I don't see anywhere on the log files on both brokers about one broker establishing a connection to the other broker.
In short, I could not bypass the port-mapper for clustering. Any ideas how ?
2) Bypassing port mapper for clustering:
I also want to bypass the port-mapper for the JMS service using the TCP protocol. I added the following:
imq.jms.tcp.port=40876
I then modified by the file object store so that the JMS client will use port 40876:
JMSConnectionFactory/RefAddr/44/Content=mq\://192.168.0.75\:7676/jms,mq\://192.168.0.188\:7676/jms
Added 40876 to be allowed by iptables. Restarted all brokers on the cluster ... but alas, the JMS clients time-out during connection.
