It looks like you're running out of file locks at the operating system
level. You'll have to do a bit of research to see what the default
resource limit is for the max number of file locks allowed on your
operating system and see how to change it. This can happen whether or
not you're running wit
Here's the actual stacktrace:
2011-01-18 04:36:25,488 [main] ERROR org.apache.activemq.broker.BrokerService -
Failed to start ActiveMQ JMS Message Broker. Reason: java.io.IOException: No
locks available
java.io.IOException: No locks available
at sun.nio.ch.FileChannelImpl.lock0(Native Me
I have a Continuous Integration system that runs on an NFS mount. I'm getting
errors about ActiveMQ not being able to obtain a lock, which I've seen before
in my code coverage tools, due to our NFS mount.
The only broker we have running during a CI test case is a VM broker, so I
tried appendin
I ended up switching to use the resource adapter provided by activemq that
comes in the lib/optional directory.
In case anyone is interested, here are the steps I followed to get it
working
asadmin create-resource-adapter-config --property
ServerUrl=failover\:(tcp\://localhost\:61616,tcp\://loca
I had a similar issue earlier. I think I fixed it by adding the following
section to my sun-ejb-jar
activemqrar
Dest
Documentation (http://activemq.apache.org/selectors.html) states the
following:
" Using XPath to filter messages
Apache ActiveMQ also supports XPath based selectors when working with
messages containing XML bodies. To use an XPath selector use the following
syntax
XPATH '//title[@lang=''eng'']' "
