You'll need to play with the polling settings.
The default settings don't actually do any real polling, instead
the http request sits inside the server waiting for a message,
occuping a thread.
<!-- length of time to wait inside server -->
<!-- length of time to wait on the client before
trying the server again -->
Okay Adrian, thanks for the response.
I just want to try to understand what's happening while I'm trying to fix it.
What you're saying is that the HTTPILServlet is basically opening a session/thread on the Tomcat instance and it will keep that open waiting for a response until it times out?
If this is the case I have a quick question - is that the best way to do things? Wouldn't it be better to just have the client side implementation for JMS send some sort of session ID so that the HTTPILServlet doesn't have to keep a thread or any other resources sitting around to service a client? This way you can get a lot more throughput through HTTP/JMS.
Just a thought :) I'm going to dig through the source and see if I can understand how that servlet is functioning because I may want to go another route to get the most through the HTTP binding.
I don't think you understood my post.
client -> tomcat (waits 60 seconds for message)
no message return to client (waits 0 seconds)
Change the parameters I mentioned above.