[
http://jira.jboss.com/jira/browse/JBREM-824?page=all ]
David Lloyd closed JBREM-824.
-----------------------------
Fix Version/s: (was: 3.0.0.Alpha1 (Otter))
Resolution: Done
Assignee: (was: Trustin Lee)
Won't fix in the 2.x series. Remoting 3 has a management interface defined in the
roadmap; see JBREM-827.
Allow server to shut down connections from specified clients
------------------------------------------------------------
Key: JBREM-824
URL:
http://jira.jboss.com/jira/browse/JBREM-824
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
From Jay Howell:
Several customers have asked for a management method to drop client connections from the
server by ip address and by client id.
So there would be two cases.
By ipaddress - this would stop the pinger and also close all connections associated
with that client ip address. Only one pinger exists for an ip address, so this would
require closing of the pinger connection also.
By clientid - this would close the pinger thread only if there are no other
connections present.
In each of the cases, clients should get an asynchronous onException call.
This facility would be necessary to support JBMESSAGING-1117.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira