AM Session DB - Sun GlassFish(tm) Message Queue 4.4

We know Sun GlassFish(tm) Message Queue 4.4 is the underlying message queue for OpenAM Session DB.

I was deploying AM Session DB a week ago when I was at customer's site. It was supposed to be a 3-nodes MQ message cluster.

The 1st day of deployment was not that enjoyable.

I kept hitting the following warning messages:



[15/Nov/2012:18:32:28 ICT] [B1004]: Starting the cluster service using tcp [ amnode1/172.19.176.115:50582 ] with min threads 1 and max threads of 1 
[15/Nov/2012:18:32:28 ICT] [B1228]: Cluster ping interval is 60 seconds
[15/Nov/2012:18:32:28 ICT] [B1039]: Broker "ambroker@192.168.1.115:7676" ready.
[15/Nov/2012:18:32:28 ICT] WARNING [B2105]: Attempting to initiate a cluster connection to mq://192.168.1.116:7676/?instName=???&brokerSessionUID=null failed: No route to host
[15/Nov/2012:18:32:28 ICT] WARNING [B2105]: Attempting to initiate a cluster connection to mq://192.168.1.117:7676/?instName=???&brokerSessionUID=null failed: No route to host
[15/Nov/2012:18:35:48 ICT] WARNING [B2105]: Attempting to initiate a cluster connection to mq://192.168.1.116:7676/?instName=???&brokerSessionUID=null failed: No route to host
[15/Nov/2012:18:35:49 ICT] WARNING [B2105]: Attempting to initiate a cluster connection to mq://192.168.1.117:7676/?instName=???&brokerSessionUID=null failed: No route to host


Note at this point of time, I had not configured OpenAM to use AM Session DB yet. My intention was to make sure that the 3-nodes cluster is working properly.

The log was not showing something I wanted it to show. So I spent a considerable amount of time to debug, and that includes asking the Unix team to loosen the rules in the OS's iptable (see here). Yet, after the firewall rule was loosen, I kept getting the same warning messages.

I called it a day then. Too tired, too hungry.

The next day when I came back, I was getting the same warning messages again and again. That's when I changed strategy. Maybe I should just configure OpenAM for Session Failover to see whether if there's any luck.

Bingo!



[16/Nov/2012:10:06:30 ICT] [B1179]: Activated broker 
Address = mq://192.168.1.117:7676/?instName=ambroker&brokerSessionUID=6143819218583616768
StartTime = 1353034753349
ProtocolVersion = 410 
[16/Nov/2012:10:06:30 ICT] [B1071]: Established cluster connection to broker mq://192.168.1.117:7676/?instName=ambroker&brokerSessionUID=6143819218583616768[/192.168.1.117:37897]
[16/Nov/2012:10:06:30 ICT] [B1179]: Activated broker 
Address = mq://192.168.1.116:7676/?instName=ambroker&brokerSessionUID=6894512981523671040
StartTime = 1353034959341
ProtocolVersion = 410 
[16/Nov/2012:10:06:30 ICT] [B1071]: Established cluster connection to broker mq://192.168.1.116:7676/?instName=ambroker&brokerSessionUID=6894512981523671040[/192.168.1.116:57351]
[16/Nov/2012:10:11:07 ICT] [B1173]: Received GOODBYE [mq://192.168.1.117:7676/?instName=ambroker&brokerSessionUID=6143819218583616768] from mq://192.168.1.117:7676/?instName=ambroker&brokerSessionUID=6143819218583616768
[16/Nov/2012:10:11:07 ICT] [B1072]: Closed cluster connection to broker mq://192.168.1.117:7676/?instName=ambroker&brokerSessionUID=6143819218583616768
[16/Nov/2012:10:11:07 ICT] [B1180]: Deactivated broker 
Address = mq://192.168.1.117:7676/?instName=ambroker&brokerSessionUID=6143819218583616768
StartTime = 1353034753349
ProtocolVersion = 410 
[16/Nov/2012:10:12:32 ICT] [B1179]: Activated broker 
Address = mq://192.168.1.117:7676/?instName=ambroker&brokerSessionUID=5327541786327008256
StartTime = 1353035551372
ProtocolVersion = 410 
[16/Nov/2012:10:12:32 ICT] [B1071]: Established cluster connection to broker mq://192.168.1.117:7676/?instName=ambroker&brokerSessionUID=5327541786327008256[/192.168.1.117:51002]

So, that warning messages could simply be ignored. I still have no idea what the hell are those messages for. They are super mis-leading! I do not seem to see them in my previous deployments. 

.