| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ5.3 client occasional broken pipe to a remote 5.3 QM |
« View previous topic :: View next topic » |
| Author |
Message
|
| Pat Fleming |
 Posted: Tue Jul 10, 2007 5:10 am Post subject: MQ5.3 client occasional broken pipe to a remote 5.3 QM |
 |
|
Newbie
Joined: 16 Oct 2003
Posts: 8
|
Hi,
I've built a daemon process using the GNU C++ compiler which runs on a solaris 2.9 host using the MQ5.3 client library. This daemon process puts a message to a local queue in a remote QM. It is stable most of the time but occasionally crashes and logs the following:
[i]06/29 17:04:21 Broken pipe from sockRead(): 'procname' (0x62114927/31)[/i]
While this message is a log message in our own format, it looks like there is some sort of underlying IP error. As I say, it doesn't happen all the time and messages are normally put correctly to the queue. It appears to happen under load. There are many daemon processes putting to a single queue.
My question is if anyone observed this behaviour, especially under load? In looking at this, if I've not put enough information in the post don't hesitate to ask.
Thanks
Pat |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jul 10, 2007 5:13 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Is anything logged by the queue manager when this happens? Like a channel error?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Pat Fleming |
| Posted: Wed Jul 11, 2007 2:42 am Post subject: |
|
|
Newbie
Joined: 16 Oct 2003
Posts: 8
|
Hi Vitor,
Thanks for having a look at this. The QM doesn't seem to have logged anything indicating there was any issue with any channel at the time the broken pipe was reported in the client.
Thanks
Pat |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 11, 2007 2:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Ok, so what TCP/IP socket is your process listening on, and to what purpose?
It doesn't on the face of it sound like an MQ issue. If there is a problem and no channel error it sounds like something the MCA can auto-recover from.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
