You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2016/02/01 21:12:39 UTC

[jira] [Commented] (AMQ-6140) 2016-01-24 13:02:01,501 | WARN | Exception occurred processing: CONNECT accept-version:1.0,1.1 heart-beat:10000,30000

    [ https://issues.apache.org/jira/browse/AMQ-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126938#comment-15126938 ] 

Timothy Bish commented on AMQ-6140:
-----------------------------------

The error indicates that you have a client with the given ID already connected to the broker, this is not a broker problem it is properly rejecting clients with duplicate IDs

> 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)