You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomee.apache.org by Dain Sundstrom <da...@iq80.com> on 2008/01/10 22:22:44 UTC

ActiveMQ persistence config (removed Derby dep)

I have finally figured out how to get ActiveMQ to use our database  
pool instead of letting it create it's own (Derby).  To configure the  
datasource that ActiveMQ uses to store persistent messages, simply  
set the following property on the ActiveMQ resouce adapter in the  
OpenEJB conf file:

     # DataSource for persistence messages
     DataSource Default Unmanaged JDBC Database

If the property is null (empty), you get in memory persistence.

Also, since ActiveMQ was the sole user of Derby, we no longer have a  
dependency on the 2M Derby jar. This means the the tomcat war is a  
mere 13M now!

-dain

Re: ActiveMQ persistence config (removed Derby dep)

Posted by Jacek Laskowski <ja...@laskowski.net.pl>.

On Jan 10, 2008 10:22 PM, Dain Sundstrom <da...@iq80.com> wrote:

> Also, since ActiveMQ was the sole user of Derby, we no longer have a
> dependency on the 2M Derby jar. This means the the tomcat war is a
> mere 13M now!

Yay! That sounds great at the merest ;-)

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl