[
https://issues.apache.org/jira/browse/AMQ-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-6140.
-----------------------------
Resolution: Not A Problem
>From the error given this is the case of multiple client connect attempts with
>the same client ID. Suggest you retest with a later broker version which have
>some improvements for detecting and removing client connection attempts that
>failed. You might also need to tune your keep alive timeouts to detect a
>client drop faster.
> 2016-01-24 13:02:01,501 | WARN | Exception occurred processing: CONNECT
> accept-version:1.0,1.1 heart-beat:10000,30000
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-6140
> URL: https://issues.apache.org/jira/browse/AMQ-6140
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-camel
> Affects Versions: 5.10.0
> Environment: Windows 2008 R2
> Reporter: Sujit Ramakrishnan
> Fix For: 5.10.0
>
>
> I have multiple clients connecting to MQ server via Tomcat server.
> I have been facing the below errors monthly once and restart of MQ and Tomcat
> services resolves this issue.
> 2016-01-24 13:02:01,502 | WARN | Transport Connection to:
> tcp://10.144.x.x:53851 failed: java.io.IOException: Broker: localhost -
> Client: FlushOldMessages1:02:01 PM already connected from
> tcp://10.145.x.x:62356 |
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
