MQSeries.net :: View topic - MB v6.1 HTTP Listener Issue

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 » MB v6.1 HTTP Listener Issue

MB v6.1 HTTP Listener Issue

« View previous topic :: View next topic »

Author

Message

RBMW

Posted: Tue Apr 12, 2011 10:21 pm Post subject: MB v6.1 HTTP Listener Issue

Newbie

Joined: 12 Apr 2011
Posts: 2

Hi,

Most of our message transaction is using HTTP protocol. The version of MB used is MBv6.1. Normal scenario everything working perfect. But during trmendous load, HTTP listener is not able to pick few of the transactional messages. Hence message is getting timeout.

We have increased the instance of the flow but still the problem persist.
We understand that the broker version could be migrated from v6.1 to 7 for better performance of http. But this migration will include a major application which cannot happen immediately.

To overcome this http listener problem, is there any other alternatiove ?Could anyone help.

Thanks

gfrench

Posted: Tue Apr 12, 2011 11:16 pm Post subject:

Acolyte

Joined: 10 Feb 2002
Posts: 71

It would be useful for you to give us the symptoms and what you see going on. How many http flows have you? How many http flows per execution group? Are they pure http or soap over http? If the later you could use the execution group listener instead of the single broker listener. You can also trace the listener to see what its doing.

Have you played around with the properties of the HTTP Listener? It looks like you can play around with the maximum number of threads the broker keeps for the listener and the maximum number of sessions it keeps open. It could have reached the limit and binned some requests.

Just some thoughts really, but might help.

RBMW

Posted: Wed Apr 13, 2011 10:56 am Post subject:

Newbie

Joined: 12 Apr 2011
Posts: 2

Hi,

Thanks a lot for ur valuable thoughts.

All transactional message flows input is from Message queue. But the source applications cannot connect to MB using MQ. The mode of communication from source applications is HTTP(pure HTTP). So we have a gateway flow that accepts the HTTP message and drops them into transactional flows input queue.

The number of instance of HTTP gateway flow running is 7..

During peak load, few messages from source application is not picked up by the HTTP gateway flow. So the messages are getting timed out.

we are trying to increase the max threads of the HTTP listener. What can be the maximum number of thread ?

Can any external HTTP server introduced to increase the number of HTTP listeners ?

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MB v6.1 HTTP Listener Issue

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