Re: if DefaultMessageListenerContainer caches consumer, will it occurs situation of PooledConnectionFactory doc said

>if DefaultMessageListenerContainer caches consumer, will it occurs situation >of PooledConnectionFactory doc said? I don't know - or more to the point it doesn't really matter as one should never use a pooled connection factory of any kind in conjunction with the DMLC. The DMLC is designed such

Re: Async Writer Thread Shutdown error adding a message on 5.15.2 broker

I checked with IT guys and the disk I/O is not the issue, it can handle the data rate just fine. I did not have time in finding a way to slow the producers. Building from 5.15.x/3 branch from source is not an option at this time. I also believe [AMQ-6815 KahaDB checkpoint needs to fail fast in th

Dead lock when queue message volume is high

Hello, I have ActiveMQ setup which configured with network of brokers like below. The central ActiveMQ connects with different locations of ActiveMQ brokers in durable subscriptions for both Queue and Topic and on 20K consumers are connected with that different locations of ActiveMQ broker. There

Change Artemis 2.4.0's default credentials

Hi, Since Hawtio is integrated within Artemis 2.4.0, was wondering, how can i change the default credentials that the console comes with? Thanks, Chandra -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: [ARTEMIS] Message not being consumed from queue which came from topic using divert and selector expression

Thanks Justin, with the fix in ARTEMIS-1508 the issue is also gone for in my case. Br, Archibald -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

if DefaultMessageListenerContainer caches consumer, will it occurs situation of PooledConnectionFactory doc said

In PooledConnectionFactory doc of activemq, it is said they don't cache consumer, the reason as following: When a consumer is complete, it is best to close it rather than return it to a pool for later reuse: this is because, even if a consumer is idle, ActiveMQ will keep delivering messages to the

Re: [ARTEMIS] Message not being consumed from queue which came from topic using divert and selector expression

Based on your description I'd say it's the same issue. A fix was committed to the code-base on November 27 so it's not in any release yet (2.4.0 was released on November 7). You can try building from master and testing if you like otherwise I guess you'll need to wait until 2.5.0 is released. J

Re: dlqDeliveryFailureCause java.lang.Throwable: duplicate from store for queue

Hello Tim, Thanks for your reply. I saw that post but it mentions the following issues that don't apply to our setting: - AMQ-4485 fixed in 5.9 - AMQ-5266 jdbc store which we don't use We're using 5.10.0 : - with no network of brokers. - basic queue's and topics We're planing to use authentica

Re: Async Writer Thread Shutdown error adding a message on 5.15.2 broker

On Jan 10, 2018 12:42 PM, "neon18" wrote: We run the broker with max heap of 4G and initial of 1G (-Xmx4G -Xms1G). We use non-persistent messages on these particular queues (3 of them in this test). The number of messages sent to the broker in my last "flood gate" test was around 40,000 (40k) in

Re: Async Writer Thread Shutdown error adding a message on 5.15.2 broker

Gary, Can you elaborate on what about this situation looks like that problem? Because based on the information given so far, it looked to me like the OP was simply overdriving the storage to which the temp files are written. Tim On Jan 12, 2018 4:04 AM, "Gary Tully" wrote: > this looks like an

Re: Async Writer Thread Shutdown error adding a message on 5.15.2 broker

this looks like an instance of the regression from https://issues.apache.org/jira/browse/AMQ-6815 On Wed, 10 Jan 2018 at 19:42 neon18 wrote: > We run the broker with max heap of 4G and initial of 1G (-Xmx4G -Xms1G). > We use non-persistent messages on these particular queues (3 of them in > this