Le mer. 24 oct. 2018 à 09:23, Emmanuel Touzery <
emmanuel.touz...@lit-transit.com> a écrit :
> Hello,
>
> thank you for the answer!
>
> In this case TOMEE and AMQ are in the same process, on the same
> machine, communicating through 127.0.0.1 so network between AMQ and
> TOMEE shouldn't
Hello Emmanuel
It can be a lot of things like a network breakdown behind a proxy (so AMQ
does not see it in some cases and a restart recreates the connection), some
backpressure (exponentional), some disk issue etc...
It can be interesting to check your config for healthchecks, batch sizes,
and
Hello,
noone has any suggestion?
Regards,
emmanuel
On 22/10/2018 16:04, Emmanuel Touzery wrote:
Hello,
we have a tomee+ 7.0.3 installation with activemq, using kahadb as
a persistent message storage. We have an activemq.xml, we plugged it
though :
BrokerXmlConfig =
Hello,
sure! Regarding the runtime, we also have the postgresql driver in
lib, I think that's all. Hibernate is in our WAR for instance.
here's the activemq.xml =>
https://www.dropbox.com/s/ukttiupouyiv779/activemq.xml?dl=0
tomee.xml =>
Hello,
we have a tomee+ 7.0.3 installation with activemq, using kahadb as
a persistent message storage. We have an activemq.xml, we plugged it
though :
BrokerXmlConfig = xbean:file:/opt/app/tomee/conf/activemq.xml
in the tomee.xml. The activemq broken runs within TOMEE:
ServerUrl
