You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Eric Dayi Zhang (JIRA)" <ji...@apache.org> on 2018/07/27 09:28:00 UTC
[jira] [Updated] (AMQ-7022) warn failed:
org.apache.activemq.transport.TransportDisposedIOException: peer stopped
[ https://issues.apache.org/jira/browse/AMQ-7022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Dayi Zhang updated AMQ-7022:
---------------------------------
Issue Type: Wish (was: Bug)
> warn failed: org.apache.activemq.transport.TransportDisposedIOException: peer stopped
> -------------------------------------------------------------------------------------
>
> Key: AMQ-7022
> URL: https://issues.apache.org/jira/browse/AMQ-7022
> Project: ActiveMQ
> Issue Type: Wish
> Components: Broker
> Affects Versions: 5.10.0
> Environment: Two VMs running in HA mode, running activemq(active-standby) to transfer service massage between them and other servers.
> Reporter: Eric Dayi Zhang
> Priority: Minor
> Fix For: WAITING_FOR_TEST
>
>
> In activemq.log, below warning keeps comming out. Could anyone explain what they stand for and help me stop them? Thank you!!
> | WARN | Transport Connection to: vm://<hostname>#<port> failed: org.apache.activemq.transport.TransportDisposedIOException: peer (vm://<hostname>#<port>) stopped. | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ BrokerService[xxxx] Task-xxxxxxx
> | WARN | Transport Connection to: tcp://<hostname>:<port> failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///<hostname>:<port>@<port>
> | WARN | Could not start network bridge between: vm://<hostname>?async=false&network=true and: tcp://<hostname>:<port> due to: Connection refused | org.apache.activemq.network.DiscoveryNetworkConnector | Simple Discovery Agent-xxxx
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)