| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Random network issues causing problems |
« View previous topic :: View next topic » |
| Author |
Message
|
| KeeferG |
 Posted: Thu Jul 14, 2005 7:40 am Post subject: Random network issues causing problems |
 |
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
Looking through our logs we keep on getting the following errors occuring.
For the sending end
#define EPIPE 32 /* Broken pipe */
For the receiving end
#define EINVAL 22 /* Invalid argument */
I was wondering what would cause us to have an invalid argument.
Any thoughts
On the sending end
-------------------------------------------------------------------------------
07/14/05 00:14:48
AMQ9206: Error sending data to host ss44bsppas02 (10.251.18.32).
EXPLANATION:
An error occurred sending data over TCP/IP to ss44bsppas02 (10.251.18.32).
This
may be due to a communications failure.
-------------------------------------------------------------------------------
07/14/05 00:14:48
AMQ9206: Error sending data to host ss44bsppas02 (10.251.18.32).
EXPLANATION:
An error occurred sending data over TCP/IP to ss44bsppas02 (10.251.18.32).
This
may be due to a communications failure.
ACTION:
The return code from the TCP/IP(write) call was 32 X('20'). Record these
values
and tell your systems administrator.
----- amqccita.c : 2049
-------------------------------------------------------
07/14/05 00:14:48
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO.PP.AS02' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.PP.AS02' in the
error
files to determine the cause of the failure.
----- amqrccca.c : 883
--------------------------------------------------------
07/14/05 00:14:53
AMQ9002: Channel 'TO.PP.AS02' is starting.
EXPLANATION:
Channel 'TO.PP.AS02' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
On the receiving end
-------------------------------------------------------------------------------
07/14/05 00:14:48
AMQ9208: Error on receive from host ss44bsppar01 (10.251.18.21).
EXPLANATION:
An error occurred receiving data from ss44bsppar01 (10.251.18.21) over
TCP/IP.
This may be due to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 22 (X'16'). Record these
values
and tell the systems administrator.
----- amqccita.c : 2758
-------------------------------------------------------
07/14/05 00:14:48
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO.PP.AS02' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.PP.AS02' in the
error
files to determine the cause of the failure.
----- amqrmrsa.c : 467
--------------------------------------------------------
07/14/05 00:14:53
AMQ9002: Channel 'TO.PP.AS02' is starting.
EXPLANATION:
Channel 'TO.PP.AS02' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
 |
| malammik |
| Posted: Thu Jul 14, 2005 10:24 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
|
|
| Back to top |
|
|
| csmith28 |
| Posted: Thu Jul 14, 2005 1:46 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
As an MQSeries admin there isn't much you can do about this. If the network goes down, the network goes down.
You may want to check your system logs for possible NIC or inetd issues though.
On AIX: errpt -a | more
On Solaris: have a look at the /var/adm/messages file
On Window: Look in the System Event Viewer
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| KeeferG |
| Posted: Fri Jul 15, 2005 5:06 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
No FDC genereted. With have a look at the syslogs.
Cheers
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
|
| vinodsasidharan |
| Posted: Fri Jul 15, 2005 5:27 am Post subject: Mq behaves Bad if network is BAD . |
|
|
Apprentice
Joined: 25 Apr 2003
Posts: 47
Location: Norwich
|
Hi ,
As you can see most of your errors are related to communication or network .
This may be due to a communications failure.
If all were fine and if this is happeneing intermetently then 100 % a network issue .
When i face network issues , I capture the network latency , Any request Time outs on the Ping and submit them to my Network Team since there is Nothing we can do as MQ is highly dependent on NETWORK .
When there is a bad network Latency and if BatchSz is Too big , then it takes a long time for messages to be tramsmitted .So better to have a smaller Batsz In bad netwrok conditions . Other than these there is Nothing a Mq personel can do if network is BAD .
But there are times in a Production environment with the Network People saying "Network is 100 % fine Some issue in Mq!!!!!!!". So we need some network monitoring tools to fight back such statements.
_________________
Vinod sasidharan
Ibm Certfied MQ Admin 5.3
Ibm Certfied MQ Admin 6.0
Ibm Certfied WAS Admin 6.0
Ibm Certfied WMB Admin 5.0
Ibm Certfied Db2 Specialist.
Sun certified Java Programmer.
"Ai carte, ai parte ....................." |
|
| 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
|
|
|
|
