Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <446487101.1220356432714.JavaMail.jira@brutus>
Date: Tue, 2 Sep 2008 04:53:52 -0700 (PDT)
From: "Rob Davies (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQ-1841) Network of pure master/slave
 synchronization issue
In-Reply-To: <1009612505.1215442920304.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-1841?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies resolved AMQ-1841.
-----------------------------

    Fix Version/s: 5.2.0
       Resolution: Fixed

This is solved by SVN revision 691206?

> Network of pure master/slave synchronization issue
> --------------------------------------------------
>
>                 Key: AMQ-1841
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1841
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>         Environment: Solaris 9 jdk 1.5
>            Reporter: ying
>            Assignee: Rob Davies
>            Priority: Blocker
>             Fix For: 5.2.0
>
>
> The topology is as follows:
> Master A
> Master B
> Slave A
> Slave B
> configure the client(multiple threads of consumers and producers)  to use=
 failover (failover://(tcp://masterA, tcp://masterB)) so slaves are only us=
ed to replicate data.
> Issues:
> Start masterA, slaveA, masterB, slaveB then start the client, slaveB will=
 get IllegalStateException:
> ERROR Service                        - Async error occurred: java.lang.Il=
legalStateException: brokerSlave2
> Cannot add a consumer to a session that had not been registered: ID:usaap=
d1-32873-1215441964305-2:1:1
> java.lang.IllegalStateException: brokerSlave2 Cannot add a consumer to a =
session that had not been register
> ed: ID:usaapd1-32873-1215441964305-2:1:1
>         at org.apache.activemq.broker.TransportConnection.processAddConsu=
mer(TransportConnection.java:541)
>         at org.apache.activemq.command.ConsumerInfo.visit(ConsumerInfo.ja=
va:345)
>         at org.apache.activemq.broker.TransportConnection.service(Transpo=
rtConnection.java:310)
>         at org.apache.activemq.broker.TransportConnection$1.onCommand(Tra=
nsportConnection.java:180)
>         at org.apache.activemq.transport.ResponseCorrelator.onCommand(Res=
ponseCorrelator.java:104)
>         at org.apache.activemq.transport.TransportFilter.onCommand(Transp=
ortFilter.java:68)
>         at org.apache.activemq.transport.vm.VMTransport.iterate(VMTranspo=
rt.java:205)
>         at org.apache.activemq.thread.DedicatedTaskRunner.runTask(Dedicat=
edTaskRunner.java:98)
>         at org.apache.activemq.thread.DedicatedTaskRunner$1.run(Dedicated=
TaskRunner.java:36)
> Comments:
> The issue seems that broker masterA and masterB's DemandForwardingBridge =
started before slaveB is attached so the commands to adding connections and=
 sessions are not replicated on slaveB so the exception happens. For a netw=
ork of pure master/slave, we kinda want the following to happen in order:
> 1. master to wait for slave to be attached=20
> 2. master to accept demandforwardbridge from other master=EF=83=A0
> 3. start master transport to serve connections
> Is there anyway to enforce the above order?=20

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