[ 
https://issues.apache.org/jira/browse/AMQ-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205525#comment-13205525
 ] 

kimm king commented on AMQ-2804:
--------------------------------

derby also support for-update syntax, see 
http://db.apache.org/derby/docs/dev/ref/  select segment.
so I think it's well with derby.

notice that it's INFO, not WARN or ERROR.

if DefaultDatabaseLocker can't get a locker, it will report it, sleep a while 
and retry.

                
> Database lock driver override not found for : [oracle_jdbc_driver].  Will use 
> default implementation.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2804
>                 URL: https://issues.apache.org/jira/browse/AMQ-2804
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.2
>         Environment: 2.6.9-89.0.11.ELsmp #1 SMP Mon Aug 31 11:00:34 EDT 2009 
> x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Ramesh
>            Priority: Blocker
>
> I am trying to do activeMQ Clustering with ORACLE 
> database(master/slave).After the configuration I do see three tables created 
> in the database but I don't see data is storing in the database. In fact it's 
> storing in the activemq-data folder(default implementation). I see these 
> warnings in the log.
> INFO | Database adapter driver override recognized for : [oracle_jdbc_driver] 
> - adapter: class org.apache.activemq.store.jdbc.adapter.OracleJDBCAdapter
>  INFO | Database lock driver override not found for : [oracle_jdbc_driver].  
> Will use default implementation.
> So somehow it's not using database ?? Any help on this is greatly appreciated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to