| Author |
Message
|
| sidharth_bora |
 Posted: Sun Mar 18, 2007 10:51 pm Post subject: Strange MQ problem - |
 |
|
Voyager
Joined: 24 Nov 2005
Posts: 87
|
Hi,
We have a QM configured on AIX and a remote QM on windows 2003.
We have 4 remote queues and is using ony 1 channel to pass message back and forth.
Initially from AIX to Windows, we tested the first 3 remote queue connectivity all ok but for the last remote queue, the messag doesnt pass to the Windows QM and remains in the TQ on AIX.
Checking the log onAIX indicates as follows:
The last batch of messages could not be accepted by the remote queue manager, check the remote queue manager longs
when we check the logs of Windows 2003 QM, it says internal error occured. Also in FDC, it says the same.
Any pointers, ideas is greatly appreciated
AIX QM - 5.3 CSD11
Windows2003 MQ - 6.0
best regards
Sid |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Sun Mar 18, 2007 11:20 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
show the errors and the FDC's , lots of smart people here, but no crystalballs... 
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 19, 2007 1:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Michael Dag wrote: |
| no crystalballs |
Not since I started using the onitment.... 
Also search here and in Google for the ProbeIds you'll find in the FDC files. These may provide valuable clues to your problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| anantha sreenivasan |
| Posted: Tue Mar 20, 2007 1:15 pm Post subject: |
|
|
Acolyte
Joined: 26 Sep 2006
Posts: 72
|
Try to check the xmit q status on the AIX Server for uncommitted messages.
DIS QS(XMITQ NAME) UNCOM
If this command returns yes, it means there are uncommitted messages stalled in the xmit queue. The channel might be in retrying or in running state.
Also based on the indication by the channel log that the "target queue manager did not accept the last batch of messages", there might be a sequence number mismatch.
To solve this
ON AIX Side
a) Stop the Channel
b) resolve channel(channel name) action(backout)
c) reset channel(channel name) seqnum(1)
Now try to start the channel and the messages should have travelled across from the xmit queue.
If this situation still persists follow this step once more.
Uncommitted message issue is generally transient. MQ recovers this by itself.
If all the tries fail, recycle your AIX queue manager |
|
| Back to top |
|
|
| sidharth_bora |
| Posted: Wed Mar 21, 2007 6:59 pm Post subject: |
|
|
Voyager
Joined: 24 Nov 2005
Posts: 87
|
Hi All,
Thanks for all the valuable inputs.
Checking and analyzing the FDC's , it was found as Bad log format( we had opened a PMR with IBM) but couldnot get much details.
Has some one come across this issue earlier or could some on shed some light on bad log format.
Also checking through the server logs, it was found software communication error(communication protocol error).
Thanks is advance for your help
regds |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Wed Mar 21, 2007 11:37 pm Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
Do you have dead letter queues defined (and configured in the QMgr) on the sending and receiving QMgr?
What tells the Windows Event Log?
_________________
Regards
Hubert |
|
| Back to top |
|
|
| sidharth_bora |
| Posted: Wed Mar 28, 2007 11:10 pm Post subject: |
|
|
Voyager
Joined: 24 Nov 2005
Posts: 87
|
Hi,
Sorry for getting late on this issue.
Yes we have the DLQ defined on both the QM.
The problem is resolved, we created the QM from scratch on windows
but the query still remains unanswered...
about the bad log format...
FYI there is enough disk space and memory |
|
| Back to top |
|
|
|
|
