You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by dege <de...@pointclickcare.com> on 2006/11/10 20:45:56 UTC
Re: derby db failing on restart
Any update on this?
Thanks
dege wrote:
>
> Attached is the application log with debugging turned on
> At line 1657 is where resin starts to unload and then reload the
> application context as a result of deploying an updated class file to the
> webapps WEB-INF/classes directory.
>
> I looked at the derby.log and it is empty.
>
> In terms of configuration we use the
> org.springframework.web.context.ContextLoaderListener which loads our
> context file on startup. This context file in turn loads a local broker
>
> <bean id="broker" class="org.apache.activemq.xbean.BrokerFactoryBean">
> <property name="config"
> value="classpath:config/activemq_pcc_broker4.xml" />
> <property name="start" value="true" />
> </bean>
>
> the config file looks like the following:
>
> <beans xmlns="http://activemq.org/config/1.0">
>
> <broker useJmx="true" brokerName="pccapp" persistent="true"
> useShutdownHook="true">
> <transportConnectors>
> <transportConnector uri="vm://pccapp"/>
> </transportConnectors>
>
> <persistenceAdapter>
> <journaledJDBC journalLogFiles="5"
> dataDirectory="./pcc_messages/journal" />
> </persistenceAdapter>
>
> </broker>
> </beans>
>
>
> We also setup a some message driven pojo's pointing to a remote broker
> that isn't up which is why you see all the other connect errors. In
> development this is hardly ever up unless we are working on that part of
> the application.
>
>
> http://www.nabble.com/file/903/esolutions.log esolutions.log
>
--
View this message in context: http://www.nabble.com/derby-db-failing-on-restart-tf2142524.html#a7283881
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: derby db failing on restart
Posted by James Strachan <ja...@gmail.com>.
On 11/10/06, dege <de...@pointclickcare.com> wrote:
>
> Any update on this?
Afraid not - no idea why you're having this problem.
To simplify your hot-swap configuration it might be easier to run the
ActiveMQ broker as a separate process from your hot-swapping wars.
--
James
-------
http://radio.weblogs.com/0112098/