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 which stores messages on behalf of the JMS HTTP client. When the HTTP connection from client to server is "interruptedly killed", the instance of HTTPClientIL still exists accepting messages and store them to HTTPClientILStorageQueue. Thus any message sent to this HTTPClientIL instance is lost. When JMS HTTP client tries to "reconnect" after detecting the failure to the JMS HTTPIL server, "another" instance of HTTPClientIL is created. The first one would be "finalized" when the HTTP session is timeout on tomcat. But until then there are still JMS messages received and lost in that HTTPClientIL instance. So the current HTTPIL is good for sending JMS messages to the queues/topics but it's not good for receiving JMS messages. I have to at the end write a web service for HTTP client to poll for received JMS messages instead and persistently manage the connection to the queue/topic on the server side. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835306#3835306 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835306 ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
