|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Constant Timeouts after IP Change on the box. |
« View previous topic :: View next topic » |
Author |
Message
|
klink |
Posted: Wed Jul 28, 2004 11:37 am Post subject: Constant Timeouts after IP Change on the box. |
|
|
Newbie
Joined: 01 Aug 2003 Posts: 4
|
OK, I'll try to keep this short.
We have wmqi v2.1 w/ CSD06 and MQ v5.3 w/ CSD04 .... configmgrs on Win2k and brokers on AIX 5.2. About 10 days ago Network Services changed the IP address on our Unit/Test AIX Broker box. We proactively stopped all WMQI brokers and MQ Qmgrs on the box 1st. DNS was updated and the the IP change on the box occurred.
NOW, we are consistenly getting timeouts after about 1 - 1.5 days of activity on the box (deploys mostly). We can bring down the brokers and QMGRs and cleared shared memory, bring the brokers & qmgrs back up and we are fine for about 1-1.5 days ... deploys are fast. Then they cycle starts all over again.
I have (constantly) verified that all associated QMGRs are up and running along with the corresponding Channels to the Broker QMGRs. I have verified that the health of the box if in great shape (memory, i/o, paging space all look great). No errant or looping flows or anything to the like. Nothing on the network side to slow things down.
Points to Make: We HAVE NOT recycled the broker AIX box. The back end DB Server (DB2) had it's IP address changed at a different point in time (before the change on the broker AIX) and other apps accessing that box (and there are plenty) are not having issues. We are not having the issues in our other environments (training, stage, prod).
I took a look at IBMs MQ site to see if there were any MQ/WMQI CSDs patches that helped resolve this issue ... didn't come across anything.
I'm sure there is additional information that is needed, please let me know what I can provide. Any help at all would be greatly appreciated. I'm tired of restarting the environments every other day.
Thansk!!!!!!! |
|
Back to top |
|
 |
wooda |
Posted: Mon Aug 02, 2004 6:47 am Post subject: |
|
|
 Master
Joined: 21 Nov 2003 Posts: 265 Location: UK
|
The only thing I can think of is check all the queues on the broker QMGR to see if there is a build up of messages somewhere which may be causing this. Possibly internal WMQI messages like those which are passed between broker and configmgr. |
|
Back to top |
|
 |
wooda |
Posted: Mon Aug 02, 2004 7:25 am Post subject: |
|
|
 Master
Joined: 21 Nov 2003 Posts: 265 Location: UK
|
The only thing I can think of is check all the queues on the broker QMGR to see if there is a build up of messages somewhere which may be causing this. Possibly internal WMQI messages like those which are passed between broker and configmgr. |
|
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
|
|
|
|