activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From soloist <v.solo...@gmail.com>
Subject NullPointerException, journaledJDBC
Date Mon, 23 Jun 2008 12:48:34 GMT

Hi,
i could not decide if this is a bug or not so i needed to discuss it here to
make sure. the following is my persistenceAdapter configuration

<amq:journaledJDBC journalLogFiles="5" dataDirectory="/some/path"
dataSource="#someDS" useDatabaseLock="false" />

what i do is, i stop the context containing this broker configuration and
after the broker shuts down, there is a repeating exception:

ActiveMQ Cleanup Timer ERROR
org.apache.activemq.store.jdbc.DefaultDatabaseLocker     - Failed to update
database lock: java.lang.NullPointerException
java.lang.NullPointerException
        at
org.apache.activemq.store.jdbc.DefaultDatabaseLocker.keepAlive(DefaultDatabaseLocker.java:102)
        at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.databaseLockKeepAlive(JDBCPersistenceAdapter.java:458)
        at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter$3.run(JDBCPersistenceAdapter.java:260)
        at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
        at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
        at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
        at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
        at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
        at java.lang.Thread.run(Thread.java:595)
ActiveMQ Cleanup Timer INFO 
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter     - No longer able
to keep the exclusive lock so giving up being a master
ActiveMQ Cleanup Timer WARN 
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter     - Failed to stop
broker

I was just killing the entire application before so i did not see this
problem. 
And this does not happen when i set useDatabaseLock to true because it finds
the datasource to remove the lock but i am trying to get the lock out of the
database to the journal.

Do you have any ideas?
Thanks in advance
-- 
View this message in context: http://www.nabble.com/NullPointerException%2C-journaledJDBC-tp18067095p18067095.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message