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 SupportHTTPInput based flow - concurrent requests

Post new topicReply to topic
HTTPInput based flow - concurrent requests View previous topic :: View next topic
Author Message
PeterPotkay
PostPosted: Tue Dec 01, 2020 9:29 am Post subject: HTTPInput based flow - concurrent requests Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7641

IIB 10
HTTP Listener is enabled for the Execution Group (Integration Server)
Message flow has an HTTP Input Node.
Additional Instances is set to 0.

If that message flow is busy with transaction A, what happens when the HTTP Client posts transaction B? With MQ, the answer is obvious, the message for B waits in the MQ queue that feeds the MQInput Node. But if its HTTP based, what happens to the HTTP post for transaction B if the message flow is busy with transaction A?
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Dec 01, 2020 10:54 am Post subject: Re: HTTPInput based flow - concurrent requests Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26088
Location: Texas, USA

PeterPotkay wrote:
If that message flow is busy with transaction A, what happens when the HTTP Client posts transaction B? With MQ, the answer is obvious, the message for B waits in the MQ queue that feeds the MQInput Node. But if its HTTP based, what happens to the HTTP post for transaction B if the message flow is busy with transaction A?


It waits in the internal listener queue (not an MQ artifact) until there's a flow available to process it. If there's no space left (because transaction X just showed up and the flow is still working on B) then the HTTP client gets a status 500.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Tue Dec 01, 2020 3:27 pm Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7641

And is there anyway to check this internal queue to see how many and how long things have been waiting?


And yes, I have already voiced my opinion on why are they using HTTP to send to this flow if they care what happens, especially since the flow sends out via MQ anyway, and the client sending to it is DataPower, something that natively uses MQ very well!
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Dec 02, 2020 5:34 am Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26088
Location: Texas, USA

PeterPotkay wrote:
And is there anyway to check this internal queue to see how many and how long things have been waiting?


Urgh.

I think the monitoring stats events show the number of waiting requests, Also the mqsiproperties for the listener may do it. I've never really worried unless the client's getting a lot of 500.


PeterPotkay wrote:
And yes, I have already voiced my opinion on why are they using HTTP to send to this flow if they care what happens, especially since the flow sends out via MQ anyway, and the client sending to it is DataPower, something that natively uses MQ very well!


The customer is always right.

Even if the customer is barking mad and shouldn't be allowed out without a keeper.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
abhi_thri
PostPosted: Wed Dec 02, 2020 6:07 am Post subject: Reply with quote

Chevalier

Joined: 17 Jul 2017
Posts: 403
Location: UK

hi...for how many please try the below command,

Code:
mqsireportproperties <node> -e <integration server> -o HTTPConnector -r | grep -E url\|outstandingRequests



http://www.mqseries.net/phpBB2/viewtopic.php?t=75438&highlight=
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Dec 02, 2020 8:13 am Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26088
Location: Texas, USA

abhi_thri wrote:
hi...for how many please try the below command,

Code:
mqsireportproperties <node> -e <integration server> -o HTTPConnector -r | grep -E url\|outstandingRequests



http://www.mqseries.net/phpBB2/viewtopic.php?t=75438&highlight=


Bless you
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportHTTPInput based flow - concurrent requests
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.