Looks like this problem happens when the failover re-connect among network of
brokers (AMQ1, AMQ2, AMQ3 and AMQ4) or the consumer hangs (In this case GF
App Server nodes from 1 to 6).
Is there a way to persist the temp queue destination across connections
since I have used AMQ Pooled Connection Fa
Thanks much your reply!!
We also thought the same, but quiet interestingly there is no
OutOfMemoryError in any of the Glassfish application server(which are all
typical consumers) logs and there is enough memory (-Xmx is set to 34 GB)
for each of the node.
However, I will try to analyze the dump a
It would be good if Apache ActiveMQ developer/user can share their
experience/resolution which I am facing in Production environment now.
We are using 4 network of brokers in the provider end. They are all using
ActiveMQ 5.5.1 (along with Fuse 7.0.2). All these brokers are running in
Ubuntu OS.
T
Hi,
It would be good if Apache ActiveMQ developer/user can share their
experience/resolution which I am facing in Production environment now.
We are using 4 network of brokers in the provider end. They are all using
ActiveMQ 5.5.1 (along with Fuse 7.0.2). All these brokers are running in
Ubuntu O