Author |
Message
|
peaz |
Posted: Wed Nov 24, 2004 12:33 am Post subject: AMQ9506: Message receipt confirmation failed. |
|
|
Novice
Joined: 24 Nov 2004 Posts: 10
|
Hi I'm facing this problem from Server_A sender Channel to Server_B
The following are from the error logs.
Quote: |
-------------------------------------------------------------------------------
11/21/2004 19:47:17
AMQ9002: Channel program started.
EXPLANATION:
Channel program 'A_TO_B' started.
ACTION:
None.
-------------------------------------------------------------------------------
11/21/2004 19:47:18
AMQ9506: Message receipt confirmation failed.
EXPLANATION:
Channel 'A_TO_B' has ended because the remote queue manager did not
accept the last batch of messages.
ACTION:
The error log for the channel at the remote site will contain an explanation of
the failure. Contact the remote Systems Administrator to resolve the problem.
-------------------------------------------------------------------------------
11/21/2004 19:47:18
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'A_TO_B' ended abnormally.
ACTION:
Look at previous error messages for channel program 'A_TO_B' in the
error files to determine the cause of the failure. |
Resolving the sender channel will get the sender channel back up to running. However, once a message is sent again via the sender channel. It'll end again.
A firewall sits in between Server_A and Server_B with only the required ports opened. Currently, only the default MQ port is opened for both the servers (1414) will this cause a problem?
There is another similar connection between Server_C and Server_D that is similarly configured with a firewall in between of them. but for this server, there isn't any problem whatsoever.
I've also tried deleting and creating a new sender channel but the problem still persist.
Thanks _________________ Ken Ng - http://www.placidthoughts.com/ |
|
Back to top |
|
 |
utiti |
Posted: Wed Nov 24, 2004 2:23 am Post subject: |
|
|
Newbie
Joined: 15 Oct 2004 Posts: 2 Location: Luxembourg
|
hello
I think you've a pb of reset number to confrme this you can use this command (on channel sender and receiver):
runmqsc
dis chstatus(name_channel) curseqno
end
and if the sequence number is not the same on the two channel that's your pb !!!
So you must do (on channel sender and receiver)
runmqsc
reset chl(1)
end
by
Isa _________________ Isabelle |
|
Back to top |
|
 |
Nigelg |
Posted: Wed Nov 24, 2004 5:38 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
Quote: |
ACTION:
The error log for the channel at the remote site will contain an explanation of
the failure. Contact the remote Systems Administrator to resolve the problem.
|
So, what was the error at the remote end? |
|
Back to top |
|
 |
peaz |
Posted: Wed Nov 24, 2004 6:04 am Post subject: |
|
|
Novice
Joined: 24 Nov 2004 Posts: 10
|
acutally, i've also already tried resetting the sequence number for the channels via the GUI already. the problem still persist. any other ideas why this could be? _________________ Ken Ng - http://www.placidthoughts.com/ |
|
Back to top |
|
 |
sac063 |
Posted: Wed Nov 24, 2004 6:50 am Post subject: |
|
|
Apprentice
Joined: 23 Jan 2004 Posts: 36
|
peaz wrote: |
Currently, only the default MQ port is opened for both the servers (1414) will this cause a problem? |
The other reason could be that some receive exit is running on the receiver channel. This could be configured to accept the messages from only a particular Queue manager on a given port.
Check if there is any exit program running on the other side and if you are using the expected port number. |
|
Back to top |
|
 |
peaz |
Posted: Wed Nov 24, 2004 7:52 am Post subject: |
|
|
Novice
Joined: 24 Nov 2004 Posts: 10
|
nope. no exit programs are running on either servers.
The configuration of MQ for these two servers are fairly basic.
There basically only local queues and remote definition queues that connects to the other servers local queues. Server A passes messages to Server B via the remote definitation queues without any modification to the data whatsoever. In other words, MQ Series is being used as a transport mechanism only over the firewall.
could port blocking be causing this problem? AFAIK, only TCP port 1414 is opened between the two servers. Does MQ Series needs any other ports?
Also, I might want to add that the version running here is 5.2 CSD03. It isn't very easy to get the AM team to get it up to any other versions or CSDs. _________________ Ken Ng - http://www.placidthoughts.com/ |
|
Back to top |
|
 |
Anirud |
Posted: Wed Nov 24, 2004 7:55 am Post subject: |
|
|
 Master
Joined: 12 Feb 2004 Posts: 285 Location: Vermont
|
I don't think this is the case but one of the reasons could be that your log space is full or do not have enough space.
Check to see if there are any uncommitted messages.
and if you find any uncom(YES), try to decrease the batch size to 5 on the channel which will be 50 by default and then start your channels.
Hope this helps. |
|
Back to top |
|
 |
peaz |
Posted: Wed Nov 24, 2004 4:10 pm Post subject: |
|
|
Novice
Joined: 24 Nov 2004 Posts: 10
|
|
Back to top |
|
 |
JT |
Posted: Wed Nov 24, 2004 6:27 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003 Posts: 1564 Location: Hartford, CT.
|
Nigelg wrote: |
Quote:
ACTION:
The error log for the channel at the remote site will contain an explanation of
the failure. Contact the remote Systems Administrator to resolve the problem.
So, what was the error at the remote end? |
As Nigel suggested, have you reviewed the error logs on the remote queue manager? Potentially, this may pinpoint your problem. |
|
Back to top |
|
 |
peaz |
Posted: Wed Nov 24, 2004 7:07 pm Post subject: |
|
|
Novice
Joined: 24 Nov 2004 Posts: 10
|
Hmm. Have checked the logs on the remote end.
Could this be the problem? I don't know how to decypher them though.
Quote: |
-------------------------------------------------------------------------------
11/24/2004 21:44:37
AMQ9002: Channel program started.
EXPLANATION:
Channel program 'INSC_TO_EGATE' started.
ACTION:
None.
-------------------------------------------------------------------------------
11/24/2004 21:44:37
AMQ9565: No dead-letter queue defined.
EXPLANATION:
The queue manager 'QMGR.EGATE3' does not have a defined dead-letter queue.
ACTION:
Either correct the problem that caused the program to try and write a message
to the dead-letter queue or create a dead-letter queue for the queue manager.
-------------------------------------------------------------------------------
11/24/2004 21:44:37
AMQ9599: Program could not open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object
'Q_EGATE.CLRHOUSE_INSC_1_IN' on queue manager 'QMGR.EGATE' by user '' failed
with reason code 2087.
ACTION:
Ensure that the queue is available and retry the operation. If the message is
from a remote Queue Manager, check the Message Channel Agent User Identifier
has the correct authority.
-------------------------------------------------------------------------------
11/24/2004 21:44:37
AMQ9001: Channel program ended normally.
EXPLANATION:
Channel program 'INSC_TO_EGATE' ended normally.
ACTION:
None. |
_________________ Ken Ng - http://www.placidthoughts.com/ |
|
Back to top |
|
 |
peaz |
Posted: Wed Nov 24, 2004 7:24 pm Post subject: |
|
|
Novice
Joined: 24 Nov 2004 Posts: 10
|
GAH! I think i know where the problem is already. The Remote definition queue was set to look for QMGR.EGATE while the remote QMGR was QMGR.EGATE3!
:faint: Thanks for a the reply guys. I really appreciate all the help extended.
now.. i'm gonna get the guy that configured the queues in the 1st place.... _________________ Ken Ng - http://www.placidthoughts.com/ |
|
Back to top |
|
 |
mfuini |
Posted: Thu Jan 20, 2005 7:21 pm Post subject: Similiar Problem |
|
|
Novice
Joined: 20 Jan 2005 Posts: 15
|
I was having a similiar problem... can it be caused by anything other than a mis configuration? _________________ Mark Fuini
markfuini@yahoo.com |
|
Back to top |
|
 |
Nigelg |
Posted: Fri Jan 21, 2005 12:31 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
|
Back to top |
|
 |
|