activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Tomsic <>
Subject Re: cluster problem, journal conflict?
Date Sat, 06 May 2006 14:33:41 GMT
hmm, well, i'm only running one broker per machine
actually.  you mention that i might be initializing
the jms before the broker, but if i am, i'm not aware
of it.
i'm simply starting the broker using cmd-line
"activemq xbean:file:./foo.xml"  then ssh'ing to the
next box and doing the same.
here's my full "foo.xml" startup file, if you don't
mind taking a look to see if anything looks odd
 - thanks

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns:amq="">

    <amq:broker brokerName="brokerA" useJmx="true">


                    <amq:policyEntry topic="FOO.>">

                    <amq:policyEntry topic="Prices.>">
<amq:constantPendingMessageLimitStrategy limit="0"/>


                <constructor-arg index="0">
                    <ref bean="myJournalImpl"/>
                <constructor-arg index="1">
                <constructor-arg index="2">
                    <bean id="myTaskRunnerFactory"



            <!-- by default just auto discover the
other brokers -->


    <bean id="myJournalImpl"
        <constructor-arg index="0">
            <bean id="myFile" class="">
                <constructor-arg index="0">


--- James Strachan <> wrote:

> On 5/6/06, Paul Tomsic <> wrote:
> > there's no replication at the OS level, if that's
> what
> > you're asking.
> > no NFS magic at all, actually.  i've even tried
> > putting the journals in
> > box1:/tmp/foo, box2:/tmp/bar, box3:/tmp/baz, etc.
> >
> > so, each journal is a different directory, in that
> it
> > resides on a different machine.
> > it just seems weird that i can start box[1], then
> > box[2], but box[3] fails due to the aforementioned
> > issues.
> > any other suggestions?
> Yes - see the other scenario in the FAQ...
> basically the only way this exception occurs is if
> another process
> locks the file or you start two brokers.  So I
> suspect you are
> actually running 2 brokers in a JVM - where you
> start a JMS connection
> using the vm:// connector before  you have
> initialised the broker you
> intended to, thus causing 2 brokers to start. So any
> chance you are
> creating a JMS connection before your broker?
> --
> James
> -------

View raw message