Thank you Andy for Help.
This is what seems to be helping for now, if anyone is interested. We have
splitted the connection pool for producers and consumers. Becuase,
otherwise producers/consumers are sharing, sesstions, transancions,... And
because of the error, we figured, that maybe this is the
Matej,
This is the connection string I used on an app that runs 24/7/365 - And
so far hasn't missed a beat since 2012.
failover:(nio://IPADDRESS:PORT?soTimeout=6&daemon=true&keepAlive=true&connectionTimeout=12&wireFormat.tcpNoDelayEnabled=true&wireFormat.maxInactivityDuration=48&wi
Hello Romain and Andy.
Thanks for helping.
We have only one ActiveMQ 5.10 server not embedded. So actually we
probably want only retry. For retry I have to write the hostname twice in
Tomee (1.7 - Java 8)?
failover:(tcp://10.1.1.1:61616,tcp://10.1.1.1:61616)
Actually when restarting Active MQ,
Hi Matej,
You need to specify at least two hosts to the failover for it to work -
It works like a retry when you use the same host.
failover:(tcp://10.1.1.1:61616,tcp://10.1.1.1:61616)
However, the error you are getting is possibly a design issue in
EtaUpdateReqHandler - Never cache the con
Hi
can you share:
- versons (AMQ, TomEE)
- some code to reproduce it
?
thanks
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-10-08 14:57 GMT+02:00 Matej :
> Hello all.
Hello all.
Anyone with experience with TomEE and ActiveMQ in production. We seem to
have problems with connections hanging, some poolling problem. Tomee s
connection factory returns to the Producer already closed connections.
We have tried with
BrokerXmlConfig =
ServerUrl =
