ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Message Broker SupportMQSI v2.01 erratic behaviour

Post new topicReply to topic
MQSI v2.01 erratic behaviour View previous topic :: View next topic
Author Message
jhalstead
PostPosted: Wed Oct 17, 2001 7:54 am Post subject: Reply with quote

Master

Joined: 16 Aug 2001
Posts: 258
Location: London

Using MQSIv2.0.1 (CSD02) on AIX with Oracle & MQSeries v5.2 (CSD01). There are a number of brokers on the box. We're experiencing a very very poor level of service from MQSI(when the thing is working performance is fine! we're not running short on CPU of memory & disks aren't getting hammered).

Execution groups die and restart every few minutes.

In some cases brokers will not start the execution groups correctly:
BIP2080E are constantly returned to the syslog.
Execution Group failed to return an internal configuration Start message response within a 60 second time period. : .agent: /build/S201_EP/src/AdminAgent/ImbAdminAgent.cpp: 5475: ImbAdminAgent::getXMLResponse: :

Rebooting the box seems to sort things out for a little while .... but the problems come back!

Anyone else experienced erratic behaviour of this type? (I'm reaching out to you guys here!) Maybe you've even solved such a problem?

Jamie
Back to top
View user's profile Send private message Send e-mail
adkessell
PostPosted: Mon Oct 22, 2001 2:21 pm Post subject: Reply with quote

Novice

Joined: 29 Aug 2001
Posts: 10

I have experienced it on both V2.0.1 and V2.0.2. What I have found is that it is usually something wrong with my Message Flow which doesn't get picked up by the deployment or syntax checker in the nodes.
Back to top
View user's profile Send private message
jhalstead
PostPosted: Tue Oct 23, 2001 12:31 am Post subject: Reply with quote

Master

Joined: 16 Aug 2001
Posts: 258
Location: London

Thanks for your response, I'll double check incrementally deploying message flows.
Out of intereste we've been experiencing this problem over a number of brokers, some with only a simple NEON node message flow, i.e. no complex compute nodes in the flow which might cause problems...

Anyone else had this sort of behaviour?

Jamie
Back to top
View user's profile Send private message Send e-mail
Segs
PostPosted: Tue Oct 23, 2001 12:47 am Post subject: Reply with quote

Voyager

Joined: 04 Oct 2001
Posts: 78
Location: Zurich Financial Services

Check that if you are using SQL in any of the message flows that any variables you are using have been declared.

If they are not, they get mistaken for a structure and you'll get the "Execution Group failed to return an internal configuration Start message response within a 60 second time period" message.

Hope this helps.

Ken...
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportMQSI v2.01 erratic behaviour
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


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.