Author |
Message
|
sguruprasanna |
Posted: Thu Oct 06, 2011 2:51 pm Post subject: SOAPRequest node - setting maximum concurrent threads |
|
|
 Apprentice
Joined: 29 Jul 2002 Posts: 37
|
Hi,
I have a couple of webservices consumer flows running on broker 7.0.0.3 on Solaris, that access webservices hosted on mainframe (using service flow feature) using SOAPRequest node.
I need to set limits on certain consumer flows to restrict maximum concurrent connections to just 10. This restriction is imposed by the mainframes admin team, as we brought the CICS region down when we did load testing with default settings. I was reading this article:
http://www-01.ibm.com/support/docview.wss?uid=swg21504029
that talks about (increasing?) the concurrent connections for the SOAPInput node by adjusting the HTTPConnector settings. Since I would be using HTTP with SOAPRequest nodes, I am guessing the settings described in the article applies to SOAPRequest nodes as well, correct?
But is there a way I can limit the concurrent connections (threads) just at the SOAPRequest node instead of changing it globally for all SOAP nodes?
Thanks
Guru |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Oct 06, 2011 4:45 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
What have you read that suggests that SOAPRequest node uses any threads outside of the message flow instance?
What measurements have you taken to determine how many threads your message flow creates? |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Oct 06, 2011 7:20 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Have you talked to your MF team? What is their view on Resource restriction (keyword = TCLASS) ?
I believe this would be better handled with SOAP over MQ than SOAP over http...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
sguruprasanna |
Posted: Fri Oct 07, 2011 6:00 am Post subject: |
|
|
 Apprentice
Joined: 29 Jul 2002 Posts: 37
|
mqjeff, now that I read that technote few times, I understand that the additional instances determine the number of concurrent requests regardless of the setting on the MaxThreads.
Quote: |
Have you talked to your MF team? What is their view on Resource restriction (keyword = TCLASS) ?
I believe this would be better handled with SOAP over MQ than SOAP over http... |
I will check with them about this setting.
Thanks |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Oct 07, 2011 6:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
sguruprasanna wrote: |
mqjeff, now that I read that technote few times, I understand that the additional instances determine the number of concurrent requests regardless of the setting on the MaxThreads. |
You are still trying to find wisdom about the SOAPRequest node in a technote that is exclusively talking about the SOAPInput node.
This is not the path to wisdom. |
|
Back to top |
|
 |
sguruprasanna |
Posted: Fri Oct 07, 2011 7:17 am Post subject: |
|
|
 Apprentice
Joined: 29 Jul 2002 Posts: 37
|
Ok, have you seen one for SOAPRequest node? I could not find it..
And don't both SOAPRequest and SOAPInput node use the same HTTPConnector underneath? |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Oct 07, 2011 7:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
sguruprasanna wrote: |
And don't both SOAPRequest and SOAPInput node use the same HTTPConnector underneath? |
What have you read that suggests this is true? |
|
Back to top |
|
 |
sguruprasanna |
Posted: Fri Oct 07, 2011 8:12 am Post subject: |
|
|
 Apprentice
Joined: 29 Jul 2002 Posts: 37
|
Quote: |
And don't both SOAPRequest and SOAPInput node use the same HTTPConnector underneath? |
oops. I should not have said that.. I kind of assumed that "HTTPConnector" is used by all SOAPnodes that use HTTP transport
I assumed that way as I saw this in the information center:
Quote: |
http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/ac56650_.htm
Quote: |
SOAP nodes always use the listener that is embedded in the execution group, and only this listener; you cannot configure them to use the broker-wide listener. |
|
Quote: |
You are still trying to find wisdom about the SOAPRequest node in a technote that is exclusively talking about the SOAPInput node. |
I agree.
Quote: |
What have you read that suggests this is true? |
thanks for making me dig in to the documentation to find answers myself..
BTW, I tried a bit, but I could not find anything for the SOAPRequest node and tuning the http settings for that node.. Can you help? |
|
Back to top |
|
 |
lancelotlinc |
Posted: Fri Oct 07, 2011 8:50 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
|
Back to top |
|
 |
mqjeff |
Posted: Sat Oct 08, 2011 10:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
|
Back to top |
|
 |
|