The main problem I found with the current HTTPIL for JMS is that the server will not
know if the client is still connected or not - HTTP is stateless.
When a client is connected over HTTPIL and registers as a MessageListener for a queue,
an instance of HTTPClientIL is created on the server
I can't help people if they don't read my responses.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3835307#3835307
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3835307
It seems that even PingPeriod is set, it won't fix the problem because there is a
HTTPClientIL instance created on the JBOSS to listen on the queue on behalf of remote
HTTP JMS client - the PingTask only applied to this instance that's why PingPeriod is
turned off.
I guess that the only way
Yes, the problem with http is that is stateless. There is nothing the server
can keep open (like a tcp/ip connectio) to detect when a client fails.
The client monitor helps, but only if the client is pinging to keep the connection
alive.
Is it not just a case of setting the PingPeriod in
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3820738#3820738
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3820738
Below is my jms configuration for both UIL and HTTPIL
uil2-service.xml:
mbean
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3820586#3820586
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3820586
Have you configured a ping period?
Regards,
Adrian
