| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Auto reconnect issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| girish_tharwani |
 Posted: Tue Oct 05, 2010 10:47 pm Post subject: Auto reconnect issue |
 |
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
seup..
Running QM1 and QM2 7.0.1.2 on AIX.. and a sample JMS client on my windows destkop..
Created SVRCONN for QM1 and QM2
Created CLNTCONN for QM1 and QM2 on QM1
Copied CCDT to windows desktop
Set DefRecon=Yes in mqclient.ini
Run put call (JMS Send call) in loop in JMS client
Messages start going to QM1
Issue endmqm command for QM1
QM1 starts ending, messages start going to QM2 (so far so good)
endmqm command completes and QM1 ends, the program hangs after this. No more messages go to QM2.
issue strmqm QM1, no impact, program still hangs. Number of messages on QM1 and QM2 equal to the number where program is hanging in loop
issue endmqm QM2 now
Messages start going to QM1 !!!
Unable to explain the program hanging behaviour. Please can anyone help. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed Oct 06, 2010 5:44 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
What problem-determination steps have you performed to find out why the application is hanging?
What do you mean by 'hanging?' What does Task Manager indicate for the application?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Oct 06, 2010 6:00 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
|
| Back to top |
|
|
| girish_tharwani |
| Posted: Wed Oct 06, 2010 6:09 am Post subject: |
|
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
Yes I used endmqm -r.
Hanging as in not doing anything. It issues JMS send and control does not return back till I kill the QM2.
Nothing in client logs or QMgr logs except that QM1 and QM2 CLNTCONN ends when respective QMgrs end. |
|
| Back to top |
|
|
| girish_tharwani |
| Posted: Thu Oct 14, 2010 7:53 am Post subject: RESOLVED - Auto Reconnect issue |
|
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
Auto Reconnect does not work below v7.0.1.3.
some bug related to thread locking http://www-01.ibm.com/support/docview.wss?uid=swg1IC65324
Also, after a lot of digging in documentation, found this:
***********************************
Client reconnection is triggered by server failure, queue manager failure, network connectivity failure, and by an administrator switching over to another queue manager instance.
If you are using a multi-instance queue manager, an additional cause of client reconnection occurs when you switch control from the active queue manager instance to a standby instance.
Ending a queue manager using the default endmqm command, does not trigger automatic client reconnection. Add the -r option on the endmqm command to request automatic client reconnection, or the -s option to transfer to a standby queue manager instance after shutting down.
*****************************************
Auto reconnect is triggered with endmqm -i and endmqm -p also. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
