[
https://issues.apache.org/jira/browse/AMQ-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189250#comment-15189250
]
Christopher L. Shannon commented on AMQ-6201:
---------------------------------------------
This is expected behavior when a stream closes unexpectedly, such as when a
connection is killed improperly. That being said, calling connection.close()
should work fine and properly stop the connection first. I do not see that
exception when calling close on a connection. I would attempt to reproduce
this in a unit test if possible to show that connection.close() is causing this
issue without calling stop first because it works properly whenever I test it.
> Connection not closed correctly: java.io.EOFException
> -----------------------------------------------------
>
> Key: AMQ-6201
> URL: https://issues.apache.org/jira/browse/AMQ-6201
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: Steven Mahieu
> Priority: Minor
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The connection is not closed correctly and gives the following exception:
> Transport Connection to: tcp://{IP}:{PORT_X} failed: java.io.EOFException |
> org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
> Transport: tcp:///{IP}:{PORT_X}@{PORT}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
