Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <22308210.11661283873260394.JavaMail.jira@thor>
Date: Tue, 7 Sep 2010 11:27:40 -0400 (EDT)
From: =?UTF-8?Q?Dirk_Alexander_Sch=C3=A4fer_=28JIRA=29?= <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (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.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dirk Alexander Sch=C3=A4fer updated AMQ-2901:
----------------------------------------

    Attachment: activemq.xml

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