|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
The return code from the TCP/IP(recv) [TIMEOUT] 120 seconds |
« View previous topic :: View next topic » |
Author |
Message
|
Knowledgeq |
Posted: Wed Feb 22, 2006 8:22 am Post subject: The return code from the TCP/IP(recv) [TIMEOUT] 120 seconds |
|
|
Newbie
Joined: 22 Feb 2006 Posts: 2
|
To summarize, I configured MQ Clustering and SSL to support Credit Card Encryption Project (PCI). The project went 'live' with retail catalog the 1st week in February. As a result, the nightly batch runs occur between the hours of 1-5:00 a.m. Every morning, it appears that one of the three jobs fails. These failures are intermittent in that Job 1 may fail, and the next morning job 2 fails. Upon failure, the job is resubmitted and returns a successful completion message every time. Some other key things to note, these jobs are not utilizing persistence messaging. Addition to the failures, I have noticed the following errors in the AMQ error logs. I have exhausted all efforts trying to resolve this issue (PMR's, sniffer traces, MQ traces, reviewing tech notes, etc...). IBM believes this is a network issue. The local network team believes the issue is related to application. Obviously, everyone is blaming it on the middleware.
The following parameters are configured as well.
KeepAlive=YES
MCAAdoptAll=Yes
HBINT=60
SSL Cipher Spec=TRIPLE_DES_SHA_US (w/ self-signed certificates)
2/21/2006 03:42:17
AMQ9002: Channel 'PCI1A.MD2A' is starting.
EXPLANATION:
Channel 'PCI1A.MD2A' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
2/21/2006 03:46:48
AMQ9213: A communications error for TCP/IP occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the TCP/IP(recv) [TIMEOUT] 120 seconds call was 0 (X'0').
Record these values and tell the systems administrator.
----- amqccita.c : 2682 -------------------------------------------------------
2/21/2006 03:46:49
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'PCI1A.MD2A' ended abnormally.
ACTION:
Look at previous error messages for channel program 'PCI1A.MD2A' in the error
files to determine the cause of the failure.
----- amqrccca.c : 883 --------------------------------------------------------
2/21/2006 03:46:59
AMQ9002: Channel 'PCI1A.MD2A' is starting.
EXPLANATION:
Channel 'PCI1A.MD2A' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
2/21/2006 03:49:01
AMQ9213: A communications error for TCP/IP occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the TCP/IP(recv) [TIMEOUT] 120 seconds call was 0 (X'0').
Record these values and tell the systems administrator.
----- amqccita.c : 2682 -------------------------------------------------------
2/21/2006 03:49:01
AMQ9659: A failure occurred during SSL handshaking.
EXPLANATION:
During SSL handshaking, or associated activities, a failure occurred. The
failure is 'WebSphere MQ TCP/IP Receive Failed' and has caused WebSphere MQ
channel name 'PCI1A.MD2A' to be closed. If the name is '????' then the name is
unknown.
ACTION:
Refer to prior message in the WebSphere MQ error log for information related to
this problem.
----- amqccisn.c : 852 --------------------------------------------------------
2/21/2006 03:49:01
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'PCI1A.MD2A' ended abnormally.
ACTION:
Look at previous error messages for channel program 'PCI1A.MD2A' in the error
files to determine the cause of the failure.
----- amqrccca.c : 883 --------------------------------------------------------
2/21/2006 03:49:11
AMQ9002: Channel 'PCI1A.MD2A' is starting.
EXPLANATION:
Channel 'PCI1A.MD2A' is starting.
ACTION:
None. |
|
Back to top |
|
 |
Knowledgeq |
Posted: Thu Feb 23, 2006 12:14 pm Post subject: The return code from the TCP/IP(recv) [TIMEOUT] 120 seconds |
|
|
Newbie
Joined: 22 Feb 2006 Posts: 2
|
Is there any other channel configurations that can be made to combat this problem? Also, I noticed that the sender channels do not start-up immediately (i.e inactive to bind to start mode). Does that have anything to do will SSL (symmetric certificates), and the certificates being authenticated? Is it possible to configure the channels to started up immediately when triggered. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|