[ 
https://issues.apache.org/jira/browse/DISPATCH-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy updated DISPATCH-1275:
------------------------------------
    Description: 
Sometimes there is a need to delete/kill certain connections on which there are 
slow consumers or consumers that won't acknowledge messages.

Add functionality to the router server side code that will allow users to 
delete connections based on the connection id. The connection id can be 
obtained from the output of--
{noformat}
qdstat -c{noformat}
or
{noformat}
qdmanage QUERY --type=connection{noformat}
This JIRA involves the following tasks
 # Add two fields, adminStatus and operStatus to the *connection* entity in the 
router schema. Possible connection adminStatues are *enabled* and *deleted.* 
Possible operStatuses are *up*
 # Modify the router's c-management agent to respond to a UPDATE management 
request. A connection id must be provided to update a connection 
(adminStatus=deleted). When a client deletes a connection object, the 
connection to the peer is terminated by the router. Client will not be allowed 
to terminate inter-router connections.
 # Add policy control over who is permitted to write adminStatus (add a new 
flag at the policy group level called allowAdminStatusUpdate)

  was:
Sometimes there is a need to delete/kill certain connections on which there are 
slow consumers or consumers that won't acknowledge messages.

Add functionality to the router server side code that will allow users to 
delete connections based on the connection id. The connection id can be 
obtained from the output of--
{noformat}
qdstat -c{noformat}
or
{noformat}
qdmanage QUERY --type=connection{noformat}
This JIRA involves the following tasks
 # Add two fields, adminStatus and operStatus to the *connection* entity in the 
router schema. Possible connection adminStatues are *enabled* and *deleted.* 
Possible operStatuses are *up*
 # Modify the router's c-management agent to respond to a DELETE management 
request. A connection id must be provided to delete a connection. When a client 
deletes a connection object, the connection to the peer is terminated by the 
router. Client will not be allowed to terminate inter-router connections.
 # Add policy control over who is permitted to write adminStatus (add a new 
flag at the policy group level called allowAdminStatusUpdate)


> Enable deletion of connections based on connection id
> -----------------------------------------------------
>
>                 Key: DISPATCH-1275
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1275
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Container
>    Affects Versions: 1.5.0
>            Reporter: Ganesh Murthy
>            Assignee: Ganesh Murthy
>            Priority: Major
>
> Sometimes there is a need to delete/kill certain connections on which there 
> are slow consumers or consumers that won't acknowledge messages.
> Add functionality to the router server side code that will allow users to 
> delete connections based on the connection id. The connection id can be 
> obtained from the output of--
> {noformat}
> qdstat -c{noformat}
> or
> {noformat}
> qdmanage QUERY --type=connection{noformat}
> This JIRA involves the following tasks
>  # Add two fields, adminStatus and operStatus to the *connection* entity in 
> the router schema. Possible connection adminStatues are *enabled* and 
> *deleted.* Possible operStatuses are *up*
>  # Modify the router's c-management agent to respond to a UPDATE management 
> request. A connection id must be provided to update a connection 
> (adminStatus=deleted). When a client deletes a connection object, the 
> connection to the peer is terminated by the router. Client will not be 
> allowed to terminate inter-router connections.
>  # Add policy control over who is permitted to write adminStatus (add a new 
> flag at the policy group level called allowAdminStatusUpdate)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to