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 Index » WebSphere Message Broker (ACE) Support » Messageflow Deploy BIP2066E probs

Post new topic  Reply to topic
 Messageflow Deploy BIP2066E probs « View previous topic :: View next topic » 
Author Message
Katt
PostPosted: Tue Aug 19, 2003 8:21 am    Post subject: Messageflow Deploy BIP2066E probs Reply with quote

Newbie

Joined: 11 Jul 2003
Posts: 3

hi All,
I am working on WMQI broker and configmgr are on same win2K box and share the same queue manager. I have a problem. I have message flows working fine until recently.

But when I try to re-deploy a message flow today, the deploy timed out with the following error
Quote:

BIP2066E: Broker MQPIOB1 (UUID a6399c2a-f300-0000-0080-8d396d2b4fa7) was unable to retrieve an internal configuration response message for execution group 'INF_UPD_ISIN' within the 360 second Configuration Timeout.

This can be attributed to the flow does not complete the processing of earlier message.
I saw subsequent messages being build on SYSTEM.BROKER.EXECUTIONGROUP.QUEUE. None of the start, stop or deploy of the flows working.

Can some body help me out on this issue

regards
kat
Back to top
View user's profile Send private message
Craig B
PostPosted: Tue Aug 19, 2003 8:54 am    Post subject: Reply with quote

Partisan

Joined: 18 Jun 2003
Posts: 316
Location: UK

Sound like you have got one of your flows into an infinite loop or it is hanging for some reason. Can you look on your task manager to see if your DataFlowEngine process is running at a high cpu usage. If your message flow is in this state then you probably will need to stop your broker with the -i option. Once this has stopped, you should GET(DISABLE) the queue so that the message flow cannot pick up any new messages when the broker is restarted. If you restart the broker, the problematic flow will not be able to retrieve messages, and this will give the exeution group chance to honour the deploy requests.
_________________
Regards
Craig
Back to top
View user's profile Send private message
Katt
PostPosted: Tue Aug 19, 2003 9:14 am    Post subject: Reply with quote

Newbie

Joined: 11 Jul 2003
Posts: 3

hi Craig,
The flow is not in the indefinite loop but was waiting for response from a database call which unfortunately is not under flows control. can we set a time out on the message flow? I know that aggregate nodes do it. But is there any other way?
The CPU and memory usage is normal as there are no looping involved. But why a deploy failure would result in other deploys being not getting through?
As this is a production broker, bringing down the broker would be the last step.
regards
Kat
Back to top
View user's profile Send private message
Craig B
PostPosted: Tue Aug 19, 2003 9:51 am    Post subject: Reply with quote

Partisan

Joined: 18 Jun 2003
Posts: 316
Location: UK

Hi,

I do not believe that there is a timeout you can set on WMQI nodes that will timeout DB calls if no response has been received. The Timeout you mention on Aggregation nodes, is the length of time that the aggregation will wait for an asynchronous response. Unfortunately database calls are not asynchronous in WMQI. When the message flow issues a database call, then it will need to wait for a response from the database call.

When a deploy is issued that could affect the message flow you are dealing, then the execution group needs to quiesce the message flow so that the flow definition can be updated. If the message flow is waiting for a database call to complete, then it cannot quiesce, and therefore the deploy request cannot be satisfied.

Why does your database request not return? Does it call a stored procedure that could take a long time to process??
_________________
Regards
Craig
Back to top
View user's profile Send private message
Katt
PostPosted: Tue Aug 19, 2003 10:46 am    Post subject: Reply with quote

Newbie

Joined: 11 Jul 2003
Posts: 3

yes, Its calling a stored proc which in turn does lot of internal processing and I am dependent on the responses from these intenal procedures. They are working fine until recently, but due to some DB issues of late we are having these timing issues.

So you mean to say there is no way we can achieve a time out in a message flow for a database call ?.

regards
Kat
Back to top
View user's profile Send private message
kirani
PostPosted: Tue Aug 19, 2003 9:35 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

May be you could configure your ODBC connection to timeout after some time. I have not used this muyself, but I remember reading this somewhere.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Messageflow Deploy BIP2066E probs
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.