| Author |
Message
|
| CTDeveloper |
 Posted: Mon Mar 05, 2012 7:49 pm Post subject: TCP/IP Communications Failure |
 |
|
Newbie
Joined: 05 Mar 2012
Posts: 3
|
Here is the log entry:
| Code: |
3/5/2012 15:46:50 - Process(6820.1) User(SYSTEM) Program(PATSGetParts.exe)
AMQ9208: Error on receive from host xxxxxxxx (123.45.678.123).
EXPLANATION:
An error occurred receiving data from xxxxxxxx (123.45.678.123).
over TCP/IP.
This may be due to a communications failure.
ACTION:
The return code from the TCP/IP (recv) call was 10054 (X'2746'). Record these
values and tell the systems administrator.
----- amqccita.c : 3309 ------------------------------------------------------- |
How do I search for Posts dealing with the above types of errors.
10054 is WSAECONNRESET (or MQRC_CONNECTION_BROKEN).
Regards,
Chuck |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Mon Mar 05, 2012 8:00 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
It's quite simple, actually.
1) copy the entire line 'The return code from the TCP/IP (recv) call was 10054 (X'2746').
2) go to google
3) paste the entire line
4) click search button
When I did it, About 2,120 results (0.38 seconds) were returned, many with reference to MQ and IBM.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 06, 2012 5:33 am Post subject: Re: TCP/IP Communications Failure |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| CTDeveloper wrote: |
| How do I search for Posts dealing with the above types of errors. |
Posts on this forum? I find the Search button (top right of this page) useful for this... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqrules |
| Posted: Tue Mar 06, 2012 1:11 pm Post subject: |
|
|
Centurion
Joined: 01 Jun 2005
Posts: 100
Location: US
|
TCP/IP returnCode 10054 is usually generated when an MQ application is terminated abruptly.
MR |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Mar 06, 2012 1:31 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| mqrules wrote: |
TCP/IP returnCode 10054 is usually generated when an MQ application is terminated abruptly.
MR |
Huh?? So, you are saying that the MQ application terminating caused the TCP/IP return code 10054?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| CTDeveloper |
| Posted: Tue Mar 06, 2012 2:39 pm Post subject: TCP/IP (recv) call was 10054 (X'2746') |
|
|
Newbie
Joined: 05 Mar 2012
Posts: 3
|
Thanks for the input.
The problem seems to have corrected itself overnight.
Our MQ Communications is working flawlessly today 
Did I mention that I have a Windows Server talking TCP/IP to a UNIX box?
Could this have been caused by high TCP/IP traffic?
Regards,
Chuck |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Mar 06, 2012 3:12 pm Post subject: Re: TCP/IP (recv) call was 10054 (X'2746') |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| CTDeveloper wrote: |
The problem seems to have corrected itself overnight.
|
Did one end get rebooted overnight? Less-than-graceful reboot can produce the TCP/IP return code 10054?
Did the network change? Router reboot? Any re-cabling done?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Mar 06, 2012 9:51 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
| mqrules wrote: |
TCP/IP returnCode 10054 is usually generated when an MQ application is terminated abruptly.
MR |
Huh?? So, you are saying that the MQ application terminating caused the TCP/IP return code 10054? |
Its true. This can happend if a MQ client app terminates abnormally, forcing the TCP socket session with the queue manager to be closed, without invoking the normal MQDISC processing.
_________________
Glenn |
|
| Back to top |
|
|
| IslandEsper |
| Posted: Wed Mar 07, 2012 8:03 am Post subject: |
|
|
Newbie
Joined: 07 Mar 2012
Posts: 2
|
Will acitvatiig a channel monitor on the server side help to determine the tcp fail state ?
ie. alter qmgr-name MONQ(MEDIUM) MONQ(MEDIUM)
If so , how long will it need to be run to get stats on the channel? or it has to be online to :
dis chs ( * ) MONITOR
or those stats won't help at all with a tcp reset ?
Thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 07, 2012 8:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| IslandEsper wrote: |
| Will acitvatiig a channel monitor on the server side help to determine the tcp fail state ? |
No. It's not activating a monitor, it's switching on monitoring statistics.
| IslandEsper wrote: |
| ie. alter qmgr-name MONQ(MEDIUM) MONQ(MEDIUM) |
You only need to specify the parameter once. You also need to at least ensure it's honoured by the channel.
| IslandEsper wrote: |
| If so , how long will it need to be run to get stats on the channel? or it has to be online to : |
If the channel is running, or not stopped, stats will be produced just after Hell freezes over:
| Quote: |
| A change to this parameter takes effect only on channels started after the change occurs. Any channel started before the change to the parameter continues with the value in force at the time that the channel started. |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| IslandEsper |
| Posted: Wed Mar 07, 2012 8:16 am Post subject: |
|
|
Newbie
Joined: 07 Mar 2012
Posts: 2
|
| IslandEsper wrote: |
| ie. alter qmgr-name MONQ(MEDIUM) MONQ(MEDIUM) |
Thanks for the reply.
Sorry for the typo the second parm should be MONCHL(MEDIUM) |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 07, 2012 8:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| IslandEsper wrote: |
| Sorry for the typo the second parm should be MONCHL(MEDIUM) |
A correction I should have made. 
I said it in my head, but my fingers clearly weren't listening. MONQ does nothing for channels, only queues, and is subject to the same use case as the other parameter.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqrules |
| Posted: Wed Mar 07, 2012 12:48 pm Post subject: |
|
|
Centurion
Joined: 01 Jun 2005
Posts: 100
Location: US
|
bruce2359 said
| Quote: |
Huh?? So, you are saying that the MQ application terminating caused the TCP/IP return code 10054? |
Yes, Try it yourself. It happens all the time (i.e. TCP/IP RC 10054) when you kill the MQ Client process without diconnecting it gracefully.
MR |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 07, 2012 2:25 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Yes, you can kill an app process to get this kind of error. You can also get it by unplugging or rebooting the server, snipping the cat5 cable, firewall blocking packets, ... I'm sure there must be other ways.
If it happens all the time, you have other issues to contend with.
10054 error is a socket connection failure recognized by TCP/IP, and passed to WMQ. WMQ then, dutifully, reports the TCP failure as AMQ9208.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Mar 07, 2012 4:39 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
|
| Back to top |
|
|
|
|
