Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <26102140.66981288000001355.JavaMail.jira@thor>
Date: Mon, 25 Oct 2010 05:46:41 -0400 (EDT)
From: =?UTF-8?Q?Dirk_Alexander_Sch=C3=A4fer_=28JIRA=29?= <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Issue Comment Edited: (AMQ-2901) Repeating error of client
 on reconnect
In-Reply-To: <8343933.11441283856820361.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/activemq/browse/AMQ-2901?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D62=
803#action_62803 ]=20

Dirk Alexander Sch=C3=A4fer edited comment on AMQ-2901 at 10/25/10 5:46 AM:
-----------------------------------------------------------------------

the following looks interessting to me, too. we've got a durable topic cons=
umer configured in our muleInstanze. once the broker dies the durable topic=
 consumer is connected to, the consumer tries to reconnect and gets forward=
ed to the second broker by the load balancer. the second broker than refuse=
s the connection because it thinks that there is allready a client using th=
e specific durable topic consumer id.

ERROR 2010-10-25 08:46:35,081 [ActiveMQ Connection Executor: tcp:///w.x.y.z=
:61616] [] [] org.mule.retry.notifiers.ConnectNotifier: Failed to connect/r=
econnect: jms://topic:our.cool.topic. Root Exception was: Durable consumer =
is in use for client: ourSystem.activemq-connector.f542389b-624a-4eec-85a7-=
cecadb5ec4ae and subscriptionName: our.durable.topic.consumer#f542399b-624a=
-4eec-85a7-cecadb2ec4ae(JMS Code: null). Type: class javax.jms.JMSException

      was (Author: dialsc):
    the following looks interessting to me, too. we've got a durable topic =
cosnumer configured in our muleInstanze. once the broker dies the durable t=
opic consumer is connected to, the consumer tries to reconnect and gets for=
warded to the second broker by the load balancer. the second broker than re=
fuses the connection because it thinks that there is allready a client usin=
g the specific durable topic consumer id.

ERROR 2010-10-25 08:46:35,081 [ActiveMQ Connection Executor: tcp:///w.x.y.z=
:61616] [] [] org.mule.retry.notifiers.ConnectNotifier: Failed to connect/r=
econnect: jms://topic:our.cool.topic. Root Exception was: Durable consumer =
is in use for client: ourSystem.activemq-connector.f542389b-624a-4eec-85a7-=
cecadb5ec4ae and subscriptionName: our.durable.topic.consumer#f542399b-624a=
-4eec-85a7-cecadb2ec4ae(JMS Code: null). Type: class javax.jms.JMSException
 =20
> Repeating error of client on reconnect
> --------------------------------------
>
>                 Key: AMQ-2901
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2901
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.4.0
>         Environment: redhat linux; java 1.6
>            Reporter: Dirk Alexander Sch=C3=A4fer
>         Attachments: activemq.xml
>
>
> recently we upgraded our activeMq instanzes from 5.3.1 to 5.4.0. we also =
upgraded the client API used in our mule-based services. since that upgrade=
 we are facing with strange reconnet errors. we have a network of brokers w=
ith two instances. they are located behinde a hardware loadbalancer over wh=
ich our clients connect to the brokers. if we restart one of the brokers, t=
he clients connected to it perform a reconnect and are getting linked to th=
e other broker. in our services we use a lot of queues and topics.
> it seems that some topics are unable to reconnect randomly. on one of our=
 client machines the reconnect to a durable topic wasn't possible anymore (=
Root Exception was: Durable consumer is in use for client: myUniqueConnecto=
rName and subscriptionName: myDurableSubscriberName(JMS Code: null). Type: =
class javax.jms.JMSException ). on the other machine a reconnect to another=
, non-durable topic (Root Exception was: Channel was inactive for too long:=
 /w.x.y.z:61616. Type: class org.apache.activemq.transport.InactivityIOExce=
ption ). they did not reconnect at all until the services were restarted.
> we were not having this problems with the version 5.3.1.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.