MQSeries.net :: View topic - Handle Webservice instances

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 » Handle Webservice instances

Handle Webservice instances

« View previous topic :: View next topic »

Author

Message

broker_new

Posted: Wed Sep 10, 2008 11:46 am Post subject: Handle Webservice instances

Yatiri

Joined: 30 Nov 2006
Posts: 614
Location: Washington DC

I have gone through the following link
http://www.ibm.com/developerworks/websphere/library/techarticles/0608_braithwaite/0608_braithwaite.html.

I have exposed a message flow which takes SOAP request message builds a stored procedure call and executes it and timeout is set for 1 minute.
I have deployed on broker with default instances.

HTTPInput>>>>ComputeNode>>>>>>HTTPReply

Practically it seems like it is processing one SOAP request at a time and the requests which are coming after that are queued up in SYSTEM.BROKER.WS.INPUT queue.....

The issue here is when it is processing first message it is taking nearly 45 seconds and forcing the second message wait in SYSTEM.BROKER.WS.INPUT queue by the time second message gets processed the third message is getting timed out.

Does one instance of message flow cannot handle multiple simultaneous requests....

mgk

Posted: Wed Sep 10, 2008 1:29 pm Post subject:

Padawan

Joined: 31 Jul 2003
Posts: 1642

Well additional requests can be processed simultaneously if you set the "additionalInstances" on the flow! This equates to number of threads processing messages. By default there will only be one thread processing messages...
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.

mqjeff

Posted: Wed Sep 10, 2008 1:46 pm Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

mgk wrote:

By default there will only be one thread processing messages...

By default there will be one thread PER *Input node in the flow. Regardless of what "kind" of input node that is. If the SOAPInput node was instead an MQInput node, and the flow still took 45 seconds to process but requests were coming in every 5 seconds... messages would *still* be piling up on a queue.

This is Broker 101.

broker_new

Posted: Wed Sep 10, 2008 1:54 pm Post subject:

Yatiri

Joined: 30 Nov 2006
Posts: 614
Location: Washington DC

Actually my question is by default if we set Additional instances to 0 for the message flow and deploy it ....

How many concurrent connections broker can accept at a given point of time as per the documentation it says 250 which means the 251st client that tries to connect will get a Connection Refused response. But its not at all happening for me all the requests are piling up in the SYSTEM.BROKER.WS.INPUT queue which is making the client timeout.

http://www.ibm.com/developerworks/websphere/library/techarticles/0608_braithwaite/0608_braithwaite.html

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Handle Webservice instances

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