Just an FYI to my question below. I went back and examined my camel endpoint
configuration for JMS versus my raw DMLC configuration for non camel JMS
endpoints. The one major difference was the cache setting.
When I added this to the jmsconfig, the OOM problems on the activemq broker
went away:
Did you ever solve this problem?
I've been using atomikos, spring DMLC and activemq for several years.
Recently I started using camel and we are having this exact same problem.
With the camel endpoints polling (which effectively doubled the number of
message listener containers I previously had) e
Ok ignore my previous message as that appears to be a separate issue.
The problem with the transaction not started errors had not gone away but
was simply not occurring, it came back on Friday but I now believe I have
the root cause of the issue.
The Atomikos JTA Properties documentation defines
Hi
ok the problems seems to be that the connection is getting dropped by the
ActiveMQ broker on the server.
I have now verified that the issue occurs when ActiveMQ runs out of heap
available.
I have ran two specific tests.
Note: Although these tests do not allocate that much heap to AMQ we have
that is a little odd. All I can think of is that the underlying
connection is dropped in the exception case, wonder if that is the
case. It would cause any unprepared transactions to be rolledback.
Also, the xa start is sent async to the broker, but the timing from
the logs does not indicate a race
Hi,
first of thanks very much for the prompt suggestions. I have enabled
Atomikos, ActiveMQ, and Spring JMS logging.
The posts below show the logs both for a transaction that succeeds and one
that fails. In both cases there is nothing on the queues to consume.
In both cases the transaction is
Enable trace level logging for ActiveMQ
org.apache.activemq.transaction.XATransaction to see when the rollback
is occurring. It seems that it is occurring before the TM attempts it,
possibly as a result of returning to a pool, which would point to a
bug or misconfiguration.
I suspect the 10 thread
