:
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-deadlocks-when-publisher-tries-to-commit-tp4671888p4672177.html
Sent
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-deadlocks-when-publisher-tries-to-commit-tp4671888p4671949.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Thanks Johan, so does that mean that activemq will always keeps the messages
in memory and when memory is full nothing can be done other than consume
them?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-deadlocks-when-publisher-tries-to-commit-tp4671888p4671948
ivemq.2283324.n4.nabble.com/activemq-deadlocks-when-publisher-tries-to-commit-tp4671888p4671911.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
-deadlocks-when-publisher-tries-to-commit-tp4671888p4671911.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
nabble.com/activemq-deadlocks-when-publisher-tries-to-commit-tp4671888p4671910.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
>
>
> We got plenty of free disk space on the machine. Anyone has a clue what
> might be causing this? google search and activemq bug
fixed.
We're using activemq 5.7.0 embedded into our application.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-deadlocks-when-publisher-tries-to-commit-tp4671888.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
