Return-Path: 
 <users-return-10354-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: (qmail 93054 invoked from network); 21 Aug 2007 08:41:49 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 21 Aug 2007 08:41:49 -0000
Received: (qmail 37840 invoked by uid 500); 21 Aug 2007 08:41:46 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 37806 invoked by uid 500); 21 Aug 2007 08:41:46 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 37797 invoked by uid 99); 21 Aug 2007 08:41:46 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2007 01:41:46 -0700
X-ASF-Spam-Status: No, hits=2.6 required=10.0
	tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2007 08:41:43 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1INPIg-0008SU-Lc
	for users@activemq.apache.org; Tue, 21 Aug 2007 01:41:22 -0700
Message-ID: <12250674.post@talk.nabble.com>
Date: Tue, 21 Aug 2007 01:41:22 -0700 (PDT)
From: j0llyr0g3r <timo.roessner@wincor-nixdorf.com>
To: users@activemq.apache.org
Subject: Re: Clustering not working: JMS-Exception
In-Reply-To: <12233062.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: timo.roessner@wincor-nixdorf.com
References: <12233062.post@talk.nabble.com>
X-Virus-Checked: Checked by ClamAV on apache.org


Ok, 

problem solved....:-)

I thought that AMQ-clusters could be used with only one Uri, meaning one
cluster-node goes down and the other node "hops" in, like when using a
virtual IP with Jboss.

Well, here is how it worked for me:

Master-Broker:

<transportConnectors>
   <transportConnector  name="openwire" uri="tcp://localhost:61613"/>
</transportConnectors>

<persistenceAdapter>
   <journaledJDBC journalLogFiles="5"
dataDirectory="/opt/activemq/cluster_1/shared_data"/>
</persistenceAdapter>


Slave-Broker:

<transportConnectors>
   <transportConnector  name="openwire" uri="tcp://localhost:61616"/>
</transportConnectors>

<persistenceAdapter>
   <journaledJDBC journalLogFiles="5"
dataDirectory="/opt/activemq/cluster_1/shared_data"/>
</persistenceAdapter>

Client-Configuration

failover:(tcp://localhost:61613,tcp://localhost:61616)




j0llyr0g3r wrote:
> 
> Hey folks,
> 
> i am having a hard time trying to find out how clustering works seamlessly
> with amq.
> 
> Imagine the following situation:
> 
> -> One cluster consisting of a master and a slave broker
> -> One consumer and one producer
> -> Persistence / Clustering mechanism is filesystem-based via shared
> storage
> 
> This means the master broker has the following configuration:
> 
>     <transportConnectors>
>        <!--<transportConnector  name="stomp" uri="stomp://localhost:61616"
> />-->
>        <transportConnector  name="openwire" uri="tcp://localhost:61616" />
>     </transportConnectors>
> 
>     <persistenceAdapter>
>        <journaledJDBC journalLogFiles="5"
> dataDirectory="/opt/amq_test/cluster_1/shared_data"/>
>     </persistenceAdapter>
> 
> The slave has the same configuration:
> 
> 
>     <transportConnectors>
>        <!--<transportConnector  name="stomp" uri="stomp://localhost:61616"
> />-->
>        <transportConnector  name="openwire" uri="tcp://localhost:61616" />
>     </transportConnectors>
> 
>     <persistenceAdapter>
>        <journaledJDBC journalLogFiles="5"
> dataDirectory="/opt/amq_test/cluster_1/shared_data"/>
>     </persistenceAdapter>
> 
> Now if start the master-broker followed by the slave-broker the output of
> the slave-broker is:
> 
> INFO  faultPersistenceAdapterFactory - Journal is locked... waiting 10
> seconds for the journal to be unlocked.
> INFO  faultPersistenceAdapterFactory - Journal is locked... waiting 10
> seconds for the journal to be unlocked.
> 
> 
> So far, so good....
> 
> BUT:
> 
> If i now start my consumer and producer everything works fine, meaning
> that i see the consumer receiving the messages.
> Both producer and consumer connect with the following uri:
> 
> tcp://debln099:61616?wireFormat=openwire&transport.useAsyncSend=false&tcpNoDelay=true
> 
> But if i now stop my master broker via hitting "CTRL + c" my consumer
> quits with the message:
> 
> JMS Exception occured.  Shutting down client.
> 
> And the producer quits with a:
> 
> response from futureResponse was invalid
>         FILE: activemq/transport/ResponseCorrelator.cpp, LINE: 145
>         FILE: activemq/transport/ResponseCorrelator.cpp, LINE: 152
>         FILE: activemq/connector/openwire/OpenWireFormatNegotiator.cpp,
> LINE: 105
>         FILE: activemq/connector/openwire/OpenWireConnector.cpp, LINE:
> 1468
>         FILE: activemq/connector/openwire/OpenWireConnector.cpp, LINE: 928
>         FILE: activemq/core/ActiveMQSession.cpp, LINE: 703
>         FILE: activemq/core/ActiveMQProducer.cpp, LINE: 194
>         FILE: activemq/core/ActiveMQProducer.cpp, LINE: 149
>         FILE: activemq/core/ActiveMQProducer.cpp, LINE: 108
> -----------------------------------------------------
> Finished with the demo ignore errors from this
> point on as the sockets breaks when we shutdown.
> =====================================================
> Segmentation fault
> 
> 
> According to the documentation, i would have expected that the slave
> broker immediately takes over the database lock.
> 
> This doesn't seem to be the case....
> 
> What is going wrong here?
> 

-- 
View this message in context: http://www.nabble.com/Clustering-not-working%3A-JMS-Exception-tf4297810s2354.html#a12250674
Sent from the ActiveMQ - User mailing list archive at Nabble.com.