Re: OpenJMS 0.7.7-alpha-3 released
Eric P <[email protected]>
| Newsgroups | gmane.comp.java.openjms.user |
|---|---|
| Message-ID | <[email protected]> |
Hi ! We have installed the alpha-3 too because we needed urgently the bug fix of the receiver already registered. However, we encounter others problems. We have two tomcat 5.5.9 with an embedded openjms and our application. Each application must connect to the openjms of the other server via the HTTP Tunnel Servlet (the servers are behind a router-firewall). A thread is trying to subscribe every x seconds until the app has subscribed. If there is a disconnection (onException), we try to reconnect with the same process. When we first start the server, it works correcly. The first app retry to subscribe every X seconds until the other app is up. At this time, the two apps have subscribed to the openjms server located on the other tomcat server. When we stop the tomcat server (1), the app (2) on the still running tomcat server (2) try to reconnect. When we start the tomcat server (1), the app (2) re-subscribed correctly. BUT, and this is our problems, the app (1) failed to subscribe. It stops without exception in the connection.createTopicSession(...). With the alpha-1, it worked excepted the "already registered" bug when we retry to subscribe (it happened sometimes). Optionnal answer : what is the right way to close correctly a subscriber ? Thank you for your help and i apologies for my poor english :) Eric ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click