activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From NASGroup <>
Subject Configuredfor Oracle, but always uses auto-discovers derby
Date Tue, 01 Jul 2008 12:23:53 GMT

Hello all,  I posted this on the dev forum by mistake......

We have an app using ActiveMQ embedded in JBoss server. It  has been running
fine for 1+ years. I was tasked with getting it to use Oracle instead of
Derby. Seemed simple enough, just some minor configuration changes detailed
in the documentation. 

I made the changes and thought I had success. It intially created the DB
tables and the app worked fine....  but when I dropped the tables, I noted
that the messaging was still working. 

I reviewed the JBOSS startup I see that it always find  always
auto-discovers DERBY

12:01:29,816 INFO  [JDBCPersistenceAdapter] Database driver recognized:

 I've tried changing from the journal, to jdbcpersistence I tried naming the
actual oracle adapter so it would not have to determine it itself.... 

Anyone seen any issues like this? It's gotta be something simple.... 



Which version of the software  activemq 4.0.2 
What platform and JDK/JRE?  jre1.5 
Any particular container being used - if so what version? JBoss 4.0.4 

Your code & configuration files are often useful 


<?xml version="1.0" encoding="UTF-8"?> 

<!-- START SNIPPET: xbean --> 
<beans xmlns=""> 

  <broker brokerName="theBroker" useJmx="true" persistent="true"> 

        <!-- In ActiveMQ 4, you can setup destination policies. note: this
xml format may still change a bit --> 

          <policyEntry queue="queue.Audit"> 
                              <queue name="queue/eigDLQ"
              <strictOrderDispatchPolicy /> 
              <lastImageSubscriptionRecoveryPolicy /> 

          <policyEntry queue="queue.loadContentQueue"> 
                              <queue name="queue/eigDLQ"
              <strictOrderDispatchPolicy /> 
              <lastImageSubscriptionRecoveryPolicy /> 


            <journaledJDBC journalLogFiles="5" dataDirectory="../data"
            <jdbcPersistenceAdapter dataSource="#oracle-ds"/> 

      <!-- prefixing a connector with discovery: causes the connector to be
advertised over rendezvous --> 
      <transportConnector uri="tcp://"

  <!-- Oracle DataSource  Setup 
  <bean id="oracle-ds"
   <property name="jndiName" value="java:/QspDS"/> 
  <bean id="oracle-ds" class="org.apache.commons.dbcp.BasicDataSource"
    <property name="driverClassName"
    <property name="url" value="jdbc:oracle:thin:@"/> 
    <property name="username" value="user123"/> 
    <property name="password" value="password123"/> 
    <property name="poolPreparedStatements" value="true"/> 

JBOSS statup 

12:00:59,657 INFO  [RARDeployment] Required license terms exist, view
META-INF/ra.xml in .../deploy/activemq-r 
12:00:59,985 INFO  [XBeanXmlBeanDefinitionReader] Loading XML bean
definitions from class path resource [com/m 
12:01:00,687 INFO  [ClassPathXmlApplicationContext] Bean factory for
application context [org.apache.xbean.spr 
ltListableBeanFactory defining beans
[org.apache.activemq.xbean.XBeanBrokerService]; root of BeanFactory hiera 
12:01:00,734 INFO  [ClassPathXmlApplicationContext] 1 beans defined in
application context [org.apache.xbean.s 
12:01:00,749 INFO  [CollectionFactory] JDK 1.4+ collections available 
12:01:00,765 INFO  [ClassPathXmlApplicationContext] Unable to locate
MessageSource with name 'messageSource': 
using default
12:01:00,765 INFO  [ClassPathXmlApplicationContext] Unable to locate
ApplicationEventMulticaster with name 'ap 
plicationEventMulticaster': using default
12:01:00,765 INFO  [DefaultListableBeanFactory] Pre-instantiating singletons
in factory [org.springframework.b defining beans
 root of BeanFactory hierarchy] 
12:01:02,076 INFO  [BrokerService] ActiveMQ 4.0.2 JMS Message Broker
(localhost) is starting 
12:01:02,076 INFO  [BrokerService] For help or more information please see:
12:01:02,592 INFO  [ManagementContext] JMX consoles can connect to
12:01:29,816 INFO  [JDBCPersistenceAdapter] Database driver recognized:
12:01:35,155 INFO  [JournalPersistenceAdapter] Journal Recovery Started
from: Active Journal: using 5 x 20.0 M 
egs at: C:\HECMJBoss\bin\activemq-data\journal 
12:01:35,296 INFO  [JournalPersistenceAdapter] Journal Recovered: 0
message(s) in transactions recovered. 
12:01:35,764 INFO  [TransportServerThreadSupport] Listening for connections
at: tcp://A1CWVRC1:61616 
12:01:35,764 WARN  [MulticastDiscoveryAgent] brokerName not set 
12:01:35,951 INFO  [TransportConnector] Connector tcp://localhost:61616

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message