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 » Issue with Collector Node (Control and Multi instance)

Post new topic  Reply to topic
 Issue with Collector Node (Control and Multi instance) « View previous topic :: View next topic » 
Author Message
inder
PostPosted: Thu Jun 13, 2013 5:53 am    Post subject: Issue with Collector Node (Control and Multi instance) Reply with quote

Apprentice

Joined: 24 Mar 2003
Posts: 49
Location: USA

Here is my Problem:

I am on Message Broker 8.0.0.2 running on ZLinux

I have a flow that takes a request, propagate the message from a compute node to call a webservice multiple times depending on contents of the message, group the responses together and send an output. (I cannot change the External webservice to take all of them together. Tried not possible - Legacy)

I have a timeout setting at 10 Sec and Expiry at 25 Sec.

There are two issues I need advice upon:

1. Using a Control terminal is there a way I can say that the processing is complete? (I can send a message once all the requests were sent out to the webservice to the control terminal of Collector node. But that does not seem to work. I tried all completed collections/First collection options)

2. This is the major problem. The flow is running on two instances on two execution groups. If I send one message Its working fine. But If I load 3 or more messages one time, I am not getting responses back from collection. It becomes very slow. Am I missing any thing? Is there a known issue? Once we go live the number of instances will increase exponentially.

I almost gave up and before rising a PMR like to know any expertise advice
Back to top
View user's profile Send private message
mqjeff
PostPosted: Thu Jun 13, 2013 5:58 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

The collector node has one thread pool on the input side and a different thread pool on the output side. Increasing instances of the flow may only increase the threadpool on the input side.

Don't use the control terminal to complete a collection. Add an additional message to the collection on an additional input terminal, and use that to complete a collection (i.e. an unbounded number of inputs on one terminal, and a single input on another. once you send a message to the second terminal, the collection is complete and propagated).

Take a usertrace to debug your issue. It'll get you started on figuring out where the issue is.
Back to top
View user's profile Send private message
inder
PostPosted: Thu Jun 13, 2013 6:52 am    Post subject: Reply with quote

Apprentice

Joined: 24 Mar 2003
Posts: 49
Location: USA

Great. it worked.
Thank you for the advice.

So the thread pool after collector node. What is is dependent upon. Is there any thing we can do to increase the threads
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Issue with Collector Node (Control and Multi instance)
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.