Hi,
It seems my problem is with shutting down the broker. While running a test
suite (spring integration tests), Activemq broker does not shut down after
each test causing the lock. I also find in debugging with jetty and running
with Tomcat the same behaviour when shutting down, the broker still
see:
http://activemq.apache.org/how-do-i-turn-off-creating-an-embedded-activemq-broker-when-using-the-vm-transport.html
On 6 May 2010 15:16, Travers Snyman wrote:
>
> Hi Dejan,
> The osgi dependency in the pom did the trick. It however seems the
> connection factory starts before the broker is s
Hi Travers,
that message "Waiting to Lock the Store" indicates that some other broker is
using the store. Can you make sure you don't have any other brokers running?
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://w
Hi Dejan,
The osgi dependency in the pom did the trick. It however seems the
connection factory starts before the broker is started completely. It gets
stuck running a test suite with the following:
WARN [main] AMQPersistenceAdapter.lock(1036) | Waiting to Lock the Store
d:\activemq\data
06 May 2
Hi,
just tested it
this should be enough
org.apache.activemq
activemq-core
5.3.1
org.springframework
spring
2.5.6
org.apache.xbean
xbean-spring
3.6
to include a broker. The osgi should be included in the classpath as
ActiveMQ dependency. If it is not, add it such as
Yes I have tried this with 5.3.1 and get the same error
Instantiation of bean failed; nested exception is org.springf
ramework.beans.BeanInstantiationException: Could not instantiate bean class
[org.apache.activemq.xbean.XBeanBrokerService]: Constructor threw exception;
nested exception is java.l
Hi,
can you try
org.apache.activemq
activemq-all
5.3.1
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Th
