qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-5779) JMX plugin's server sockets should set the SO_REUSEADDR socket option
Date Wed, 21 May 2014 14:10:38 GMT

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

Keith Wall updated QPID-5779:
-----------------------------

    Status: Reviewable  (was: In Progress)

> JMX plugin's server sockets should set the SO_REUSEADDR socket option
> ---------------------------------------------------------------------
>
>                 Key: QPID-5779
>                 URL: https://issues.apache.org/jira/browse/QPID-5779
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>             Fix For: 0.29
>
>
> We see the occasionally failures on CI from PortRestTest#testPutRmiPortWithMinimumAttributes
where, after the Broker restarts under control of the test, the Broker fails to bind the JMX
Connector port.
> Investigation has suggested that the problem is that the server sockets created by Oracle's
JMX do not specify the SO_REUSEADDR socket option thus attempts to rebind the socket shortly
after a close can fail (if the socket is still in a wait state).
> The solution is to change the JMX plugin to use custom ServerSocketFactories for both
the JMX connector and RMI registry that provide a socket configured with SO_REUSEADDR set
true.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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


Mime
View raw message