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 SupportMax concurrent HTTP Requests to a Broker

Post new topicReply to topic
Max concurrent HTTP Requests to a Broker View previous topic :: View next topic
Author Message
andrewfemin
PostPosted: Thu Jan 24, 2019 12:58 am Post subject: Max concurrent HTTP Requests to a Broker Reply with quote

Acolyte

Joined: 26 Aug 2017
Posts: 50

Hi,

I'm running IIB 10.0.0.11 and I'm trying to determine exactly how many number of concurrent HTTP Inputs my broker can handle.

From this documentation, I understand that maxThreads represents the maximum number of HTTP Inputs a broker can handle and in addition it can queue a number of requests represented by acceptCount. The default values for maxThreads and acceptCount are 200 and 100 respectively. My broker is running with the default values as I haven't changed them. Also, I'm using a broker wide HTTP listener. Here's the parameters list:

Code:
$ mqsireportproperties BROKER1 -o HTTPConnector -b httplistener -r

HTTPConnector
  uuid='HTTPConnector'
  address=''
  port='7080'
  maxPostSize=''
  acceptCount=''
  compressableMimeTypes=''
  compression=''
  connectionLinger=''
  connectionTimeout=''
  maxHttpHeaderSize=''
  maxKeepAliveRequests='0'
  maxThreads=''
  minSpareThreads=''
  noCompressionUserAgents=''
  restrictedUserAgents=''
  socketBuffer=''
  tcpNoDelay='true'
  enableLookups='false'
  serverName=''
  accessLog=''
  accessLogPattern=''
  corsEnabled='false'
  corsAllowOrigins='*'
  corsAllowCredentials='false'
  corsExposeHeaders='Content-Type'
  corsMaxAge='-1'
  corsAllowMethods='GET,HEAD,POST,PUT,PATCH,DELETE,OPTIONS'
  corsAllowHeaders='Accept,Accept-Language,Content-Language,Content-Type'

BIP8071I: Successful command completion.


So, as per my understanding, if I send 301 requests at the same time, 300 should process successfully and 1 should fail. However, when I tested it I found it a bit different. Even when I sent 1000 requests concurrently, all 1000 got processed. I used Apache JMeter to send 1000 requests. I have a suspicion that JMeter may not have sent all 1000 requests truly concurrently. Though all 1000 were sent in the same second, they might have been milliseconds apart.

So I introduced a SLEEP of 100 milliseconds in the message flow which I'm hitting with the requests and tried sending 1000 requests again. This time, 630 requests were processed successfully, 60 failed with SocketTimeoutException, 47 failed with SocketException and 263 failed with ConnectException. I'm unable to explain this behaviour.

Kindly help me get a clear understanding of how this works and let me know if there are any ways to measure this accurately. Thanks in advance.
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 SupportMax concurrent HTTP Requests to a Broker
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.