| Author |
Message
|
| PaulC |
 Posted: Thu Mar 19, 2009 8:31 am Post subject: QRep Websphere MQ error |
 |
|
Novice
Joined: 13 Feb 2009
Posts: 10
|
Hi all
I have Qreplication btween 2 DB2 servers constantly failng with the following message
2009-03-19-16.25.59.632343 ASN7000I "Q Capture" : "QCAP" : "WorkerThread" : "2" subscriptions are active. "0" subscriptions are inactive. "0" subscriptions that were new and were successfully activated. "0" subscriptions that were new could not be activated and are now inactive.
2009-03-19-16.25.59.638405 ASN0572I "Q Capture" : "QCAP" : "WorkerThread" : The " " program initialized successfully.
2009-03-19-16.26.07.471677 ASN0575E "Q Capture" : "QCAP" : "WorkerThread" : The program encountered a WebSphere MQ error "2053" while issuing the WebSphere MQ command "MQPUT" on queue "QUEUE.REMOTEQ".
2009-03-19-16.26.07.475701 ASN7015E "Q Capture" : "QCAP" : "WorkerThread" : The program detected an unrecoverable WebSphere MQ error for send queue "QUEUE.REMOTEQ" of publishing or replication queue map "REPL_MAP_NAME". The error action specified for the queue map is "S".
[asnqwk] Leaving the asnqwk thread:
[asnqwk] total database transactions captured = 58
[asnqwk] total MQSeries transactions = 0
[asnqwk] total DB transactions published = 0
[asnqwk] total time WAITING for logrd = 0.249 second(s)
[asnqwk] exit rc: 6030 - Rolling back MQSeries
[waitForLogrdEnd] The logrd thread terminated with rc: 0
2009-03-19-16.26.12.586607 ASN0573I "Q Capture" : "QCAP" : "Initial" : The program was stopped.
It was all working fine this morning but now it just blows up with this error..
Any help would be most welcome.. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Mar 19, 2009 8:36 am Post subject: Re: QRep Websphere MQ error |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PaulC wrote: |
The program encountered a WebSphere MQ error "2053" while issuing the WebSphere MQ command "MQPUT" on queue "QUEUE.REMOTEQ".
|
2053 = queue full.
I'd check your channels are running.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Thu Mar 19, 2009 8:38 am Post subject: Re: QRep Websphere MQ error |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Vitor wrote: |
| PaulC wrote: |
The program encountered a WebSphere MQ error "2053" while issuing the WebSphere MQ command "MQPUT" on queue "QUEUE.REMOTEQ".
|
2053 = queue full.
I'd check your channels are running. |
.....and that the remote Q has an application consuming the messages |
|
| Back to top |
|
|
| PaulC |
| Posted: Thu Mar 19, 2009 8:44 am Post subject: |
|
|
Novice
Joined: 13 Feb 2009
Posts: 10
|
The channel status is retrying. If I try to stop the channel it says it is not currently active.
I have Qapply pulling the messages off the other end.
Also how would you go about stopping this happening in the future ? |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Thu Mar 19, 2009 8:49 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
Check the MQ error logs for clues as to why the channels are not connecting.
Also check your channel configuration (sender + reveiver) making sure they have the same name on each QM
I'm assuming there isnt a firewall between the two QMs and if there is that its allowing the connection between the 2 QMs, you can test this easy enough by doing a telnet from the sending QM to the ip of the receiver using the port as defined in the sender channel. |
|
| Back to top |
|
|
| PaulC |
| Posted: Thu Mar 19, 2009 8:55 am Post subject: |
|
|
Novice
Joined: 13 Feb 2009
Posts: 10
|
The latest error log was
Vendor :- IBM |
| Probe Id :- RM056000 |
| Application Name :- MQM |
| Component :- riiTriggerMessage |
| SCCS Info :- lib/remote/amqrifna.c, 1.95.1.4 |
| Line Number :- 948 |
| Build Date :- Aug 1 2007 |
| CMVC level :- p600-202-070801 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000433 (qcap) |
| Program Name :- runmqchi |
| Addressing mode :- 64-bit |
| Process :- 5874 |
| Thread-Process :- 5874 |
| Thread :- 1 |
| ThreadingModel :- PosixThreads |
| QueueManager :- QM |
| ConnId(1) IPCC :- 18 |
| ConnId(3) QM-P :- 4 |
| Last HQC :- 1.0.0-1516328 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- rrcE_CHANNEL_IN_USE |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9514 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9514: Channel 'Channel startup failure (20009514) |
| (CHANNEL )' is in use. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 47504690275168 2b348c306360 |
| Arith2 :- 140733704699008 7fff1e79fc80 |
| Comment1 :- Channel startup failure (20009514) (CHANNEL |
| ) | |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 19, 2009 8:59 am Post subject: Re: QRep Websphere MQ error |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| WMBDEV1 wrote: |
| .....and that the remote Q has an application consuming the messages |
The only thing consuming messages from a remote queue will be the channel MCA - hence my comment!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PaulC |
| Posted: Thu Mar 19, 2009 9:06 am Post subject: |
|
|
Novice
Joined: 13 Feb 2009
Posts: 10
|
Would deleteing and recreating the channels help ?
Edit - It didn't help.
I have 'cleared' the queues, but that doesn't seem to have worked. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 19, 2009 9:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PaulC wrote: |
| The latest error log was | |
That's not an error log, that's an FDC print. The channel can go to retry without throwing an FDC.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 19, 2009 9:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PaulC wrote: |
Would deleteing and recreating the channels help ?
|
No. Fixing the problem will.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Thu Mar 19, 2009 11:47 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| PaulC wrote: |
The channel status is retrying. If I try to stop the channel it says it is not currently active.
I have Qapply pulling the messages off the other end.
Also how would you go about stopping this happening in the future ? |
The channel will also go into Retry state if the listener is down on the destination QMgr.
Make sure the destination QMgr's listener is running.
Thanks. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 19, 2009 12:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Sam Uppu wrote: |
The channel will also go into Retry state if the listener is down on the destination QMgr.
Make sure the destination QMgr's listener is running. |
As well as all the many other reasons for a retrying channel.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Fri Mar 20, 2009 1:53 am Post subject: Re: QRep Websphere MQ error |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Vitor wrote: |
| WMBDEV1 wrote: |
| .....and that the remote Q has an application consuming the messages |
The only thing consuming messages from a remote queue will be the channel MCA - hence my comment! |
I was just checking that the remote q wasnt full stopping the channels causing the messages to sit on the xmitq of the local QM  |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 20, 2009 2:24 am Post subject: Re: QRep Websphere MQ error |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| WMBDEV1 wrote: |
| Vitor wrote: |
| WMBDEV1 wrote: |
| .....and that the remote Q has an application consuming the messages |
The only thing consuming messages from a remote queue will be the channel MCA - hence my comment! |
I was just checking that the remote q wasnt full stopping the channels causing the messages to sit on the xmitq of the local QM |
As a remote queue holds no messages it almost certainly is the xmitq that's full and is the cause of the original error. If the target queue was full on the destination you wouldn't get a queue full error on put even though the channel would (eventually) go into retry.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Fri Mar 20, 2009 2:26 am Post subject: Re: QRep Websphere MQ error |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Vitor wrote: |
| WMBDEV1 wrote: |
| Vitor wrote: |
| WMBDEV1 wrote: |
| .....and that the remote Q has an application consuming the messages |
The only thing consuming messages from a remote queue will be the channel MCA - hence my comment! |
I was just checking that the remote q wasnt full stopping the channels causing the messages to sit on the xmitq of the local QM |
As a remote queue holds no messages it almost certainly is the xmitq that's full and is the cause of the original error. If the target queue was full on the destination you wouldn't get a queue full error on put even though the channel would (eventually) go into retry.
|
terminology...... i was using remoteq and target q interchangeably.... tut tut |
|
| Back to top |
|
|
|
|
