Solved! The queries that involve ACTIVEMQ_LOCK table are "long-running transaction". With the journal and disabling database lock i can make a ActiveMQ JDBC master/slave cluster because the lock is on the journal and not in the db!!!
Many Thanks! Fuzzo wrote: > > I think i've found something... > > 2008-09-24 08:00:01.148 GMT Thread[ActiveMQ ShutdownHook,5,main] (XID = > 125), (SESSIONID = 2), > SELECT * FROM ACTIVEMQ_LOCK FOR UPDATE > ******* Table Scan ResultSet for ACTIVEMQ_LOCK at read committed isolation > level using exclusive row locking chosen by the optimizer > > This is the only unusual query i've found. > > Can this query block the checkpoint? > > > -- View this message in context: http://www.nabble.com/Embedded-Derby-and-.dat-files-tp19574483p19649514.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
