Hi Mario,
Thanks!
The problem does not occur only when ActiveMQ shuts down abnormally. It also
seems to occur when a db connection is lost due to network abnormalities,
while Active MQ is running.
Unfortunately, we do need to run in master / slave mode, so turning off db
locking as you suggest
Perhaps stating the obvious... this seems to happen when there is some
network instability and the connection to the database is lost. Because the
connection is lost, ActiveMQ is unable to release the lock.
The lock then stays on the table until Oracle is good and ready to delete
it, which can be
I'm using the journaled JDBC approach to message persistence, with Oracle. It
seems to work well most of the time. However, I'm finding that even after a
normal shutdown a lock occasionally appears to be held on the activemq_lock
table. This prevents ActiveMQ from starting up again on the next att
I'm experiencing the same or a very similar problem, although it is on
version 4.1.1, oddly enough.
In my case the broker sends messages to a durable topic with two consumers.
They both receive the message just fine.
If I then re-start the broker while leaving the clients running, the second
cli
I'm experiencing the same or a very similar problem, although it is on
version 4.1.1, oddly enough.
In my case the broker sends messages to a durable topic with two consumers.
They both receive the message just fine.
If I then re-start the broker while leaving the clients running, the second
cli
I'm experiencing the same or a very similar problem, although it is on
version 4.1.1, oddly enough.
In my case the broker sends messages to a durable topic with two consumers.
They both receive the message just fine.
If I then re-start the broker while leaving the clients running, the second
cli
I'm experiencing the same or a very similar problem, although it is on
version 4.1.1, oddly enough.
In my case the broker sends messages to a durable topic with two consumers.
They both receive the message just fine.
If I then re-start the broker while leaving the clients running, the second
cli
Just to follow up on this: I've made a local copy of
activemq-core-4.1-SNAPSHOT.xsd, with this value for the connector port
attribute of the managementContext element:
That is, I changed xs:int to xs:string. The Spring config now validates
successfully and the PropertyPlaceholderConfigure
I'd like to configure the ports in my broker from a property file using the
Ant expression syntax supported by Spring. Like this:
Although this works for the ${host.name} and ${jms.broker.port}", when I add
the management context element to
How is the "broker" element associated with the broker class?
I have this in a Spring context file:
http://www.springframework.org/schema/beans";
xmlns:amq="http://activemq.org/config/1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.springframew
10 matches
Mail list logo
