[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1117) Request for feature to close connections on server side by ip address and by connection id

[Tim Fox (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1117?page=all ]

Tim Fox updated JBMESSAGING-1117:
---------------------------------

    Fix Version/s: Unscheduled

> Request for feature to close connections on server side by ip address and by connection id
> ------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1117
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1117
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Configuration and Management
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> 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 closging 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.  
> The person writing the client will have to have this in mind.  If a client has 1000 connections and the connection logic on the client reconnects.  When the server drops the ip address, then that machine will try to reconnect all 1000 clients.  I really depends on how the connection pooling on the client works.  

-- 
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