I tested out the example of the JBoss Remoting transporter. The failover seems to have a bug. I am using JBoss Remoting 1.4.0 Beta
Here is the sequence I tried: 1. Start SocketServer 2. Start HTTPServer 3. Start RMIServer 4. Start Client. I can see all the requests from Client is processed correctly. 5. Stop SocketServer. The failover works. The Client requrests are now processed by the HTTPServer. 6. Start SocketServer again. Now, all the Client requests went to the new SocketServer instead of the HTTPServer. I consider it's bug. 7. Stop SocketServer again. The Client requests cannot be processed any more. I got a lot of exception in the Client side indicating "connection refused". I am not sure why it didn't failover to the HTTPServer or the RMIServer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916094#3916094 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916094 ------------------------------------------------------- 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 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
