qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-5514) [Java Web Management] Deleting AMQP port does not close the underlying socket
Date Fri, 31 Jan 2014 23:36:09 GMT

    [ https://issues.apache.org/jira/browse/QPID-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888311#comment-13888311
] 

ASF subversion and git services commented on QPID-5514:
-------------------------------------------------------

Commit 1563343 from [~k-wall] in branch 'qpid/trunk'
[ https://svn.apache.org/r1563343 ]

QPID-5514: [Java Broker Documentation] Change ports section to note that fact that only HTTP/JMX
ports remain listening after port deletion.

> [Java Web Management] Deleting AMQP port does not close the underlying socket
> -----------------------------------------------------------------------------
>
>                 Key: QPID-5514
>                 URL: https://issues.apache.org/jira/browse/QPID-5514
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.27
>            Reporter: Keith Wall
>
> If I delete an AMQP port from using the web management console (or REST interface), the
port is apparently deleted successfully, but the port remains bound and the transport active.
> This defect currently has little impact on the end user as the model contains a rule
that prevents ports numbers from being reused during the lifespan of a broker's execution.
 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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


Mime
View raw message