I am very confused here...
We have a small issue on quering the queues... but from what I saw the
CPU issue was on your usage of whatever logger framework you were
using. I'm not sure what we can do there.
On Tue, Apr 11, 2017 at 11:11 AM, alessandro.zann...@bticino.it
wrote:
> Hello,
>
> we'
I'm facing the same problem and after 2-3 days, ActiveMQ stopped because of
OutOfMemoryError on broker side:
After doing some research, I have some theories:
- TCP connection with EOFException cannot be closed.
- Each TCP connection was run under a separate thread, so the thread cannot
be destro
The next thing I'd do is the suggestion from my earlier email to use JMX to
see what the broker thinks is going on with that queue.
I'd also confirm that the consumer is properly configured to ack messages,
either via auto-ack (the default behavior) or via some form of manual acks
(check that your
I'm upgrading from ActiveMQ 5.4.2 to 5.13.0 and dropped the newer
activemq-all.jar file into our application. When we restart the app, I'm seeing
this exception:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'org.apache.activemq.xbean.XBeanBrokerService#
Hi Tim,
I have verified that we have connected and working consumer for both queues.
But still messages were not processed. ActiveMq.log file is not point
towards any warning or error during this transaction.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Same-messa
Sorry for not getting back to you sooner.
With your configuration, messages sent to oldqueuename should be enqueued
on oldqueuename and also a new message that's a copy of the original should
be enqueued on newqueuename. In both cases, the message will show as
enqueued and will only show as dequeu
@Mtaylor
@clebert
Any news for us ?
Thanks.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Apache-Artemis-Stress-test-time-tp4723999p4724924.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
