The slave is a standby that will once it can lock the journal reverse the
roles, so
the downed node once it is up will start looking for the lock.
On Jan 8, 2013, at 9:38 AM, pico denis.pique...@londonlife.com wrote:
configured 2 brokers using the shared file syntax
However, the slave broker is always looking for the database connection and
is not starting up.
Is this the expected behavior?
Log from the slave broker
INFO | jvm 1| 2013/01/08 10:14:40 | INFO | Database
\\servername\Shared-Queue\data\kahadb\lock is locked... waiting 10 seconds
for the database to be unlocked. Reason: java.io.IOException: File
'\\Ssmsftd1\Shared-Queue\data\kahadb\lock' could not be locked.
INFO | jvm 1| 2013/01/08 10:14:50 | INFO | Database
\\servername\Shared-Queue\data\kahadb\lock is locked... waiting 10 seconds
for the database to be unlocked. Reason: java.io.IOException: File
'\\Ssmsftd1\Shared-Queue\data\kahadb\lock' could not be locked.
INFO | jvm 1| 2013/01/08 10:15:00 | INFO | Database
\\servername\Shared-Queue\data\kahadb\lock is locked... waiting 10 seconds
for the database to be unlocked. Reason: java.io.IOException: File
'\\Ssmsftd1\Shared-Queue\data\kahadb\lock' could not be locked.
INFO | jvm 1| 2013/01/08 10:15:10 | INFO | Database
\\servername\Shared-Queue\data\kahadb\lock is locked... waiting 10 seconds
for the database to be unlocked. Reason: java.io.IOException: File
'\\Ssmsftd1\Shared-Queue\data\kahadb\lock' could not be locked.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/SHARED-FILE-SYSTEM-MASTER-SLAVE-newb-tp4661492.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
