| Author |
Message
|
| nitin.wankhede |
 Posted: Mon Dec 19, 2005 3:26 am Post subject: Error AMQ9213 |
 |
|
Newbie
Joined: 19 Dec 2005
Posts: 2
Location: Pune
|
Hi All,
I have WMQ server running on HP-UX box which is communicating with WMQ configured on Win2k.While communicating some messages are getting lost in Network. ie. I am not able to recieve all the messages where as I am able to post all the messages to remote queue.
I am getting following error frequently in my MQ log.
-------------------------------------------------------------------------------
12/19/05 13:38:47
AMQ9213: A communications error for TCP/IP occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the TCP/IP(select) [TIMEOUT] 360 seconds call was 246
(X'F6'). Record these values and tell the systems administrator.
----- amqccita.c : 3074 -------------------------------------------------------
12/19/05 13:38:47
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO.HOSTQMGR' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.HOSTQMGR' in the error
files to determine the cause of the failure.
----- amqrmrsa.c : 463 --------------------------------------------------------
Can any body help me out
Thanks in Advance
_________________
Nitin Wankhede |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Dec 19, 2005 3:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Well,
Did you tell your System and Network Admin??
What was their answer ?
 |
|
| Back to top |
|
|
| nitin.wankhede |
| Posted: Mon Dec 19, 2005 9:35 pm Post subject: AMQ9213 |
|
|
Newbie
Joined: 19 Dec 2005
Posts: 2
Location: Pune
|
Their reply was that there is no problem with TCP/IP.This seems to be appln. problem as they are gettin the ping continuosly
_________________
Nitin Wankhede |
|
| Back to top |
|
|
| Carl Bloy |
| Posted: Tue Dec 20, 2005 2:10 am Post subject: This may help? |
|
|
Acolyte
Joined: 16 Dec 2003
Posts: 69
Location: England
|
|
| Back to top |
|
|
| Carl Bloy |
| Posted: Tue Dec 20, 2005 2:13 am Post subject: A tip |
|
|
Acolyte
Joined: 16 Dec 2003
Posts: 69
Location: England
|
A good tip would be to not upset the network guys and do some groundwork first to find out the exact problem. Don't forget we need them, but they don't need us! Just my opinion.
_________________
Regards
Carl |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Dec 20, 2005 4:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Their network is useless without things to use it.
It's really a joint dependancy.
But the network team should be able to look for changes or issues on their side at the same time as nitin.wankhede is looking for more information on the MQ side.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Carl Bloy |
| Posted: Tue Dec 20, 2005 5:34 am Post subject: |
|
|
Acolyte
Joined: 16 Dec 2003
Posts: 69
Location: England
|
Very true it is a joint dependency, but as i'm sure you know from Experience people are too quick too look elsewhere rather than on their own doorstep first. How many times have you been told MQ isn't working when it's an application issue? same goes for the network team.
So drawing on Experience I try and exhaust all options if possible to make sure it's not an MQ issue before hasssling other teams. If it's an urgent problem then yes I would involve other teams asap to get the quickest resoloution possible.
One thing nitin.wankhede you could try when you get this issue is telnet to the port MQ is listeneing on to see if you get a connection if you do chances are its not a network problem unless its an intermittent one.
_________________
Regards
Carl |
|
| Back to top |
|
|
|
|
