[jira] [Commented] (AMQ-5322) Message is assigned to different client with the same JMSXGroupID

[ https://issues.apache.org/jira/browse/AMQ-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098052#comment-14098052 ] Luoh Ren-Shan commented on AMQ-5322: We suspect that MessageGroupHashBucket should not u

[jira] [Updated] (AMQ-5322) Message is assigned to different client with the same JMSXGroupID

[ https://issues.apache.org/jira/browse/AMQ-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luoh Ren-Shan updated AMQ-5322: --- Attachment: GroupIdTest.java fails when N > 1024 > Message is assigned to different client with the sa

[jira] [Commented] (AMQ-5322) Message is assigned to different client with the same JMSXGroupID

[ https://issues.apache.org/jira/browse/AMQ-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098036#comment-14098036 ] Luoh Ren-Shan commented on AMQ-5322: Here is a JUnit test case to reproduce it. Please s

Build failed in Jenkins: ActiveMQ-Trunk-Deploy #1029

See Changes: [tabish121] https://issues.apache.org/jira/browse/AMQ-5072 [tabish121] Make comments match reality. -- [...truncated 14710 lines...] [JENKINS] Archiving

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: Performance Test Plugin #1029

See -- [INFO] [INFO]

[jira] [Resolved] (AMQCPP-543) message producer send never blocking when using producer flow control

[ https://issues.apache.org/jira/browse/AMQCPP-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-543. - Resolution: Fixed Fix Version/s: 3.9.0 Applied fix on trunk. > message producer send neve

[jira] [Closed] (AMQ-5034) ActiveMQ xsd missing readThreads attribute on LevelDB store

[ https://issues.apache.org/jira/browse/AMQ-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5034. - Resolution: Not a Problem Removed non-existent property from LevelDB documentation. > ActiveMQ xsd missing

[jira] [Closed] (AMQ-5040) Issue with Eclipse Paho mobile client and reconnecting due to failure.

[ https://issues.apache.org/jira/browse/AMQ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5040. - Resolution: Not a Problem The latest release has many improvements in the area of MQTT. Try the latest sn

[jira] [Commented] (AMQ-5185) Duplicate messages occur for MQTT cleanSession=false client with network of brokers

[ https://issues.apache.org/jira/browse/AMQ-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097317#comment-14097317 ] Timothy Bish commented on AMQ-5185: --- This can be worked around by using the virtual topic

[jira] [Commented] (AMQ-5322) Message is assigned to different client with the same JMSXGroupID

[ https://issues.apache.org/jira/browse/AMQ-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097261#comment-14097261 ] Timothy Bish commented on AMQ-5322: --- It would be a good idea for you to try and create a J

[jira] [Resolved] (AMQCPP-549) Potential memory leak in consumer when delivering delayed ack.

[ https://issues.apache.org/jira/browse/AMQCPP-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-549. - Resolution: Fixed Ensure that returned future pointer gets deleted. Fixed on trunk and 3.8.x >

[jira] [Created] (AMQCPP-549) Potential memory leak in consumer when delivering delayed ack.

Timothy Bish created AMQCPP-549: --- Summary: Potential memory leak in consumer when delivering delayed ack. Key: AMQCPP-549 URL: https://issues.apache.org/jira/browse/AMQCPP-549 Project: ActiveMQ C++ Clie

[jira] [Resolved] (AMQ-5072) Support configuring a different directory for the KahaDB index files.

[ https://issues.apache.org/jira/browse/AMQ-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5072. --- Resolution: Fixed Fixed on trunk, test added. > Support configuring a different directory for the Kaha

[jira] [Reopened] (AMQ-5072) Support configuring a different directory for the KahaDB index files.

[ https://issues.apache.org/jira/browse/AMQ-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reopened AMQ-5072: --- Assignee: Timothy Bish (was: Hiram Chirino) Fix needs accessors added to the KahaDBPersistenceAdapte

[jira] [Updated] (AMQ-5072) Support configuring a different directory for the KahaDB index files.

[ https://issues.apache.org/jira/browse/AMQ-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5072: -- Fix Version/s: (was: 5.10.0) 5.11.0 > Support configuring a different directory fo

[jira] [Commented] (AMQ-3098) Failed to page in more queue messages - Cannot consume messages

[ https://issues.apache.org/jira/browse/AMQ-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096788#comment-14096788 ] Laszlo Hornyak commented on AMQ-3098: - Accidentally ran into this issue when a disk fill

[jira] [Updated] (AMQ-5322) Message is assigned to different client with the same JMSXGroupID

[ https://issues.apache.org/jira/browse/AMQ-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wesley lin updated AMQ-5322: Description: I discovered since AMQ 5.9, message could be sent to different consumer even with JMSXGroupID i

[jira] [Created] (AMQ-5322) Message is assigned to different client with the same JMSXGroupID

wesley lin created AMQ-5322: --- Summary: Message is assigned to different client with the same JMSXGroupID Key: AMQ-5322 URL: https://issues.apache.org/jira/browse/AMQ-5322 Project: ActiveMQ Issue T