Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <559725613.1252738932457.JavaMail.jira@brutus>
Date: Sat, 12 Sep 2009 00:02:12 -0700 (PDT)
From: "Rob Davies (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQ-1711) IllegalArgumentException-Subscripiton
 does not exist when client disconnects
In-Reply-To: <805271323.1210038463718.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/activemq/browse/AMQ-1711?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies resolved AMQ-1711.
-----------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 5.4.0)
                   5.3.0
         Assignee: Rob Davies

> IllegalArgumentException-Subscripiton does not exist when client disconne=
cts=20
> -------------------------------------------------------------------------=
----
>
>                 Key: AMQ-1711
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1711
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.1.1
>            Reporter: Howard Orner
>            Assignee: Rob Davies
>             Fix For: 5.3.0
>
>
> When a client disconnects in a Network of Brokers configuration, it is po=
ssible for an IllegalArgumentException to be thrown from org.apache.activem=
q.broker.region.AbstractRegion.acknowlege() due to a race condition between=
 message processing and disconnect subscription clean-up.  It is easily rep=
roducable by putting two brokers in a Network of Brokers configuration (We =
will call them A and B).  If you publish message at a high rate to broker A=
 (I found that if I published messages at the rate of 1 every 10ms this hap=
pened consistantly -- better hardware may require a high rate so I recommen=
d pushing message as fast as possible), put a subscriber on broker B (my su=
bscriber used selectors but I don't think that makes a difference), and kil=
l the subscriber process (I don't know if a friendly disconnect behaves bet=
ter), Broker A will throw an exception and disconnect broker B perminately =
from the NOB configuration.  All future connections to broker B will not re=
ceived messages published to A.
> I found that if I changed AbstractRegion.acknowledge to log the error, bu=
t not throw an exception that it solved the problem with seemly no ill effe=
cts. =20

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