[jira] [Closed] (AMQ-5313) ActiveMq consumer intermittently hanging after reconnect

[ https://issues.apache.org/jira/browse/AMQ-5313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne Irwin closed AMQ-5313. Resolution: Fixed Fix Version/s: 5.9.1 A change was made in ActiveMQ 5.9.1 in that the currentCacheSize

[jira] [Commented] (AMQ-5313) ActiveMq consumer intermittently hanging after reconnect

[ https://issues.apache.org/jira/browse/AMQ-5313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136132#comment-14136132 ] Wayne Irwin commented on AMQ-5313: -- Narrowed problem down to the use a LinkedHashMap as a M

[jira] [Updated] (AMQ-5362) Consider a consumer slow if messages expire before it processes them

[ https://issues.apache.org/jira/browse/AMQ-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Bain updated AMQ-5362: -- Description: If a consumer is consistently consuming messages slower than the producer is producing them and the

[jira] [Updated] (AMQ-5361) Allow for multiple slow consumer strategies to be used together

[ https://issues.apache.org/jira/browse/AMQ-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Bain updated AMQ-5361: -- Description: AMQ-378 allowed a pluggable policy for aborting consumers that were slow, where a consumer was slow

[jira] [Created] (AMQ-5362) Consider a consumer slow if messages expire before it processes them

Tim Bain created AMQ-5362: - Summary: Consider a consumer slow if messages expire before it processes them Key: AMQ-5362 URL: https://issues.apache.org/jira/browse/AMQ-5362 Project: ActiveMQ Issue Ty

[jira] [Created] (AMQ-5361) Allow for multiple slow consumer strategies to be used together

Tim Bain created AMQ-5361: - Summary: Allow for multiple slow consumer strategies to be used together Key: AMQ-5361 URL: https://issues.apache.org/jira/browse/AMQ-5361 Project: ActiveMQ Issue Type: I

[jira] [Commented] (AMQ-5358) MQTT Durable subscription broken in 5.10 and 5.11

[ https://issues.apache.org/jira/browse/AMQ-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135657#comment-14135657 ] AR commented on AMQ-5358: - I don't think the spec is wrong. I meant that the MQTT implementation in

Stuck Messges when the JMXGroupId used

Hi, We configured JMXGroupId for our messages. But some of the messages get stucked in AMQ broker without consuming. Note : we are using AMQ 5.9.0 Is there any solution to get rid of the issue. Thanks in advance! Stuck Messges when the JMXGroupId used -- View this message in context: http:

[jira] [Resolved] (AMQ-5360) mqtt-doc: Wild card mapping tables in the doc is wrong

[ https://issues.apache.org/jira/browse/AMQ-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5360. --- Resolution: Fixed > mqtt-doc: Wild card mapping tables in the doc is wrong > ---

[ANNOUNCE] Apache.NMS.ActiveMQ 1.6.4 Released

Hello The Apache.NMS.ActiveMQ 1.6.4 Release bundle is now available. This is a bugfix release that includes some stability fixes for issues found since the v1.6.3 release along with a hardening of the local transaction support for MessageConsumer instances. The Wiki Page for this release is

[jira] [Assigned] (AMQ-5155) Heartbeat fails in STOMP over WebSockets

[ https://issues.apache.org/jira/browse/AMQ-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac reassigned AMQ-5155: -- Assignee: Dejan Bosanac > Heartbeat fails in STOMP over WebSockets >

[jira] [Created] (AMQ-5360) mqtt-doc: Wild card mapping tables in the doc is wrong

Joe Luo created AMQ-5360: Summary: mqtt-doc: Wild card mapping tables in the doc is wrong Key: AMQ-5360 URL: https://issues.apache.org/jira/browse/AMQ-5360 Project: ActiveMQ Issue Type: Bug

Stuck Messges when the JMXGroupId used

Hi, We configured JMXGroupId for our messages. But some of the messages get stucked in AMQ broker without consuming. Note : we are using AMQ 5.9.0 Is there any solution to get rid of the issue. Thanks in advance! -- View this message in context: http://activemq.2283324.n4.nabble.com/Stuck-

More CPU utilization in 5.9.0

Hi, I configured transacted for the consumer as true, so it's cache level is CACHE_NONE. But here lots of dynamic forward consumers are getting created and advisory messages are created more. This cause the high utilization of CPU, even upto 100% for single core m/c. My activemq version : 5.9.0

[jira] [Created] (AMQ-5359) DefaultDatabaseLocker is incompatible with Postgresql

Peter Tillemans created AMQ-5359: Summary: DefaultDatabaseLocker is incompatible with Postgresql Key: AMQ-5359 URL: https://issues.apache.org/jira/browse/AMQ-5359 Project: ActiveMQ Issue Type