| Author |
Message
|
| Andarivadu |
 Posted: Wed Jul 13, 2005 6:04 am Post subject: REQUESTER-SERVER Channel Pair |
 |
|
Novice
Joined: 18 Apr 2005
Posts: 11
|
All,
Environment : WebSphere MQ 5.3 CSD05 on XP and AIX.
I have a REQUESTER-SERVER Channel Pair. REQUESTER on XP, SERVER on AIX. Recently we made some changes to XP System so that XP System will go into HYBERNATION after 15 minutes or so. Now we are facing problems with this Channel pair after this change.
Sometimes when XP System comes out of HYBERNATION, the REQUESTER Channel is still in RUNNING status, but the SERVER channel on AIX is going to RETRYING status. This makes sense because the DISCOENCT INTERVAL for the SERVER Channel is 4 minutes.
Presently, I have to FORCE STOP the REQUESTER CHANNEL and start it again to have both channels up and running. I thought of using AdoptNewMca but it doesn't work for REQUESTER Channels.
Any inputs will be appreciated.
Thanks |
|
| Back to top |
|
 |
| sebastianhirt |
| Posted: Wed Jul 13, 2005 6:28 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
Hi,
This is not realy surprising. If the Workstaion goes to Hybernating, it is physically switched off. During this period the content of the RAM is somehow stored to the HDD, and reloaded when restarted.
That is also why the requester is still running. Nothing has changed for it after the 'restart'.
Your server channel should go back to running after the retry/ long retry intervall.
If it doesn't you might want to check the IBM homepage. Maybe this is a known problem, that has been fixed in a CSD after 5.
My personal opinion, is that it is a bad idea to let a MQ Server go to Hybernating at all.
my 2 cents
Sebastian |
|
| Back to top |
|
|
| Andarivadu |
| Posted: Wed Jul 13, 2005 7:02 am Post subject: |
|
|
Novice
Joined: 18 Apr 2005
Posts: 11
|
Sebastian :
Thanks for the reply. As you said its not surprising me too.
| Quote: |
| Your server channel should go back to running after the retry/ long retry intervall. |
The problem here is the REQUESTER Channel maintaining its RUNNING Status, and not accepting new connection from SERVER (my guess). |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jul 13, 2005 7:13 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Before you try anything and dig deep into this have you given a thought to
| Quote: |
| that it is a bad idea to let a MQ Server go to Hybernating at all. |
|
|
| Back to top |
|
|
| Andarivadu |
| Posted: Wed Jul 13, 2005 7:16 am Post subject: |
|
|
Novice
Joined: 18 Apr 2005
Posts: 11
|
Vennela:
Yaa, I forgot to mention in my last post, that HYBERNATION thing is not in our hands. The Client needs it for some other reasons. |
|
| Back to top |
|
|
| sebastianhirt |
| Posted: Wed Jul 13, 2005 7:20 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
| Quote: |
| The Client needs it for some other reasons. |
 Eventually they discovered how to make a Windows System save |
|
| Back to top |
|
|
| hguapluas |
| Posted: Wed Jul 13, 2005 8:53 am Post subject: |
|
|
Centurion
Joined: 05 Aug 2004
Posts: 105
Location: San Diego
|
Hybernation can also impact your network connection. Sometimes that gets broken in hybernation which may be contributing to the problem of one end maintaining a running status while the other goes into retry.
Have you thought of some sort of triggering event that resets/cycles the "hybernating" channel on wakeup? |
|
| Back to top |
|
|
| Andarivadu |
| Posted: Fri Jul 15, 2005 6:32 am Post subject: |
|
|
Novice
Joined: 18 Apr 2005
Posts: 11
|
Thanks for all your replies guys.
I am thinking, as hguapluas said, some sort of triggering event that resets/cycles the "hybernating" channel on wakeup. |
|
| Back to top |
|
|
| malammik |
| Posted: Fri Jul 15, 2005 7:34 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
|
I assume that the XP box that goes into hybernate mode runs mq client. Not the server. When the your machine goes into hibernate mode windows sends a signal to all processes and they indeed can choose to perfrorm a certain action before the process if offloaded. Your app should be a service and listening for those signals. Stop the channel when it receives and restart the channel when it is activated or simply check the channel once in a while.
_________________
Mikhail Malamud
http://www.netflexity.com
http://groups.google.com/group/qflex |
|
| Back to top |
|
|
|
|
