MQSeries.net :: View topic - application bug: bipbroker

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » application bug: bipbroker

application bug: bipbroker

« View previous topic :: View next topic »

Author

Message

rell13

Posted: Mon Feb 03, 2014 9:38 am Post subject: application bug: bipbroker

Newbie

Joined: 03 Feb 2014
Posts: 2

Hi, All,

I am new to WebSphere and we are encountering an issue with PROD environment. Our network connectivity was lost and many applications was affected including our MQ Broker. After the link was restored, I saw these lines on the /var/log/messages of our server repeating all over again:

Feb 3 11:14:35 our_hostxxx kernel: application bug: bipbroker(14924) has SIGCHLD set to SIG_IGN but calls wait().
Feb 3 11:14:35 our_hostxxx kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.

Can someone help me explain what these lines mean? Please see additional info below.

linux version: 2.4.21-27.ELsmp
mq version: Websphere Message Broker version 5

Vitor

Posted: Mon Feb 03, 2014 9:47 am Post subject: Re: application bug: bipbroker

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Found your problem:

rell13 wrote:

mq version: Websphere Message Broker version 5

Version 5? Seriously? Did you miss the memo about the 21st Century starting?

Those lines almost certainly mean something's hosed up in the broker connectivity & you should restart to see if that helps.

Or just live the problem and accept that you'll see many, many more as v5 slowly decomposes under you.

v6 is now out of support. And v5 wasn't all that when it was new.
_________________
Honesty is the best policy.
Insanity is the best defence.

smdavies99

Posted: Mon Feb 03, 2014 11:58 am Post subject:

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Let me add my 2p worth to this discussion.

I worked on a V5 project. V5 was the first 're-engineered' toolkit version that used Eclipse. The V5.0.0. runtime was frankly worse than V2.1.
5.0.0.3 sort of worked but as soon as V6 came out we moved to it. Far more stable.

I have to ask if this system has anything to do with the recent spate of questions in another forum on this site relating to WMQ 5.1

Broker V5 went out of support a good few years ago. Its sucessor (V6) also is not longer supported and even the sucessor to that has gone to the great out of support graveyard in thep sky.
If your production system is really still runnong on V5, I am truly puzzled about what has being happening at that site in the years since it was supported. Did the customer get a case of 'tight-fistedness' and not pay for support? It is not unknown for that to happen.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » application bug: bipbroker

Jump to:

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

Protected by Anti-Spam ACP