First off am not sure why you are not seeing an exception when making the following call:
client.removeListener(listener); Upon making this call on the client, the client will remove the listener from the callback server and the target server. Since the callback server has been destroyed, should get a org.jboss.remoting.CannotConnectException thrown. Just to make sure there wasn't a bug with disconnecting callbacks, I wrote a test case to verify that once callback listener is removed and the callback server is destroyed, that no more callbacks are delivered (based off the code you posted in the forum). The test classes are org.jboss.test.remoting.callback.push.disconnect.CallbackTestClient and org.jboss.test.remoting.callback.push.disconnect.CallbackTestServer. The test passes on my machine with latest remoting codebase. Also, was able to debug to make sure that there were no threads left over that shouldn't be and there were not. If you still think this is an issue, please open a jira issue and supply a test case demonstrating the bug. Thanks. -Tom View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921585#3921585 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921585 ------------------------------------------------------- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
