| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CCDT failback to primary |
« View previous topic :: View next topic » |
| Author |
Message
|
| vivica12 |
 Posted: Thu Feb 12, 2009 8:33 am Post subject: CCDT failback to primary |
 |
|
Acolyte
Joined: 13 Jul 2007
Posts: 58
|
I'm trying to find any documentation anywhere that lets me know if a java app will failback to it's primary server when using a CCDT file for failover.
Scenario. QM1 and QM2. App is WAS6 using JMS connection factories, and CCDT configured. The failover process works seemlessly - if QM1 fails the app keeps right on going using QM2. So what happens once QM1 is available again? Will the app/connection factory retry QM1 since it is the primary, or do you have to force it back to primary? I know that I can go back if I make QM2 fail, but wondered if there was a retry interval for the primary. (when I say primary, it is the server that I have configured to be alphabetically first by channel name - on purpose)
I swear I have read about it somewhere, but I"ve spent the past few hours trying to find it again, to provide business documentation, and I can't find it. Any help would be appreciated.
_________________
Vivica - signing off |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Feb 12, 2009 8:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| If the connection to QM2 is working, why should the app close that? |
|
| Back to top |
|
|
| vivica12 |
| Posted: Thu Feb 12, 2009 9:20 am Post subject: |
|
|
Acolyte
Joined: 13 Jul 2007
Posts: 58
|
Honestly, business decision.
Our QM1 and QM2 are at our primary site and secondary site. The secondary site has more delay over network etc. So for those and other similar reasons they want processing to be at primary if primary is available.
_________________
Vivica - signing off |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Feb 12, 2009 9:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Unless something causes MQ to notice that the connection to QM2 is not available, then nothing will likely cause the connection to disconnect from QM2.
If the connection to QM2 ends normally, and QM1 is available when another connection is asked for...
The problem you'll run into is that you'll have worse performance on QM2 than you would otherwise, if you are doing things to cause the QCFs to periodically disconnect and attempt to reconnect to QM1, as long as QM1 is unavailable.
You could maybe do something to cause connections to be reset (wsadmin scripting perhaps) when QM1 comes back on line. |
|
| 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
|
|
|
|
