Is that the full stack trace?  Because that line uses a nested exception:

throw new Exception(broker.getStartException())

The nature of that nested exception might give you a clue as to what
is going on.

On Tue, Mar 17, 2015 at 10:37 AM, nohaapav <pavol.n...@gmail.com> wrote:
> Hi,
>
> i'm facing problem with JDBC failover scenario. Using version 5.11.1.
>
> Have two brokers:
> -broker1 running on server01.no:61616
> -broker2 running on server02.no:61616
>
> and 1 shared oracle database.
> When broker1 starts = become a master and lock the DB, when broker2 starts
> become a slave and waiting till lock is released. After approximatelly 10
> minutes of trying to acquire lock slave just shut down:
>
>  INFO | broker2 Lease held by broker1 till Tue Mar 17 15:00:03 CET 2015
>  INFO | broker2 failed to acquire lease.  Sleeping for 16000 milli(s) before
> trying again...
>  INFO | broker2 Lease held by broker1 till Tue Mar 17 15:00:18 CET 2015
>  INFO | broker2 failed to acquire lease.  Sleeping for 16000 milli(s) before
> trying again...
> ERROR: java.lang.Exception
> java.lang.Exception
>         at
> org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:96)
>         at
> org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
>         at
> org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:150)
>         at
> org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
>         at
> org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:606)
>         at org.apache.activemq.console.Main.runTaskClass(Main.java:262)
>         at org.apache.activemq.console.Main.main(Main.java:115)
>
> Pretty much out of ideas what is going wrong here. Failover is working
> pretty fine, but if slave is waiting 10+ minutes then bash process fail and
> broker is not running anymore.
>
>
>
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/JDBC-Failover-Slave-shutting-down-tp4693374.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to