[jira] [Closed] (PROTON-1254) Proton-J opens redundant sockets during reconnect and never frees those resources

["Zoltan Varga (JIRA)" <ji...@apache.org>]

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

Zoltan Varga closed PROTON-1254.
--------------------------------
    Resolution: Invalid

The issue was in the upper layer, how the Proton-J close() was handled.
The upper layer used "  if (this.state != State.CLOSED)" check to free the resources. It looks like client code has to call close() for all proton-j layers regardless the state. 



> Proton-J opens redundant sockets during reconnect and never frees those resources
> ---------------------------------------------------------------------------------
>
>                 Key: PROTON-1254
>                 URL: https://issues.apache.org/jira/browse/PROTON-1254
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-j
>    Affects Versions: 0.13.0
>         Environment: Java 1.8 (latest) on Windows and Linux
>            Reporter: Zoltan Varga
>
> Repro:
> - Run TCPView (WIndows) or use TcpDump on Linux 
> - Start sending AMQP messages to pier
> - Disconnect network cable
> - Connect network cable again
> - Repeat the two steps above several times
> - Check the sockets opened and held by the Java process for the used remote address/port
> Notice there are sockets left opened in undefined state (either ESTABLISHED or CLOSE_WAIT)
> The redundant sockets will be never released. Only exiting the application will release them. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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