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 » Slow First Request - for Http Input Node.

Post new topic  Reply to topic
 Slow First Request - for Http Input Node. « View previous topic :: View next topic » 
Author Message
wilsonjohn24
PostPosted: Mon Jul 07, 2008 1:50 am    Post subject: Slow First Request - for Http Input Node. Reply with quote

Voyager

Joined: 02 Feb 2007
Posts: 93
Location: Scotland

Hi,

Have a scenario in which a flow is doing http -> transform -> MQ.

However on first request ( or request after a period of no activity - about 10 mins ) it takes on average 1 second longer. In our production scenario - this is not acceptable.

It seems to be the biphttplistener that has an overhead- as when we run a MQ -> transform-> MQ we dont have the issue.

I appreciate that it is good working practices to "move out" components that have not been accessed in X seconds. But in this situation I need to keep this in an always active state.

Any help appreciated in tweaking biphttplistener?

thanks in advance


John
Back to top
View user's profile Send private message
sridhsri
PostPosted: Mon Jul 07, 2008 11:02 am    Post subject: Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

I found this information in a developerWorks article. I am not sure if this will help you:

There is a configurable property called maxKeepAliveRequests that specifies how many requests can be send down a single connection.

The default Message Broker value is 100. Therefore, when an HTTP client connects, it can send 100 requests before Message Broker issues a Connection: close and closes the socket. The next request the client sends creates a new socket and again can send up to 100 requests. In many environments this setting may be enough. But when maximum throughput is required, you may need to set this value higher or make it unlimited, in order to achieve the desired throughput.

Here is the command: mqsichangeproperties MyBroker -b httplistener -o HTTPConnector -n maxKeepAliveRequests -v 0

It is supported only when you select HTTP 1.1

You will find more information at: http://www.ibm.com/developerworks/websphere/library/techarticles/0608_braithwaite/0608_braithwaite.html
Back to top
View user's profile Send private message
wilsonjohn24
PostPosted: Tue Jul 15, 2008 2:30 am    Post subject: Reply with quote

Voyager

Joined: 02 Feb 2007
Posts: 93
Location: Scotland

thanks for that,.;...
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 » Slow First Request - for Http Input Node.
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.