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

See -- [INFO] [INFO]

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

See Changes: [tabish121] https://issues.apache.org/jira/browse/AMQ-5323 -- [...truncated 14694 lines...] [JENKINS] Archiving

[jira] [Closed] (AMQ-4985) java.util.ConcurrentModificationException while sending message

[ https://issues.apache.org/jira/browse/AMQ-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-4985. - Resolution: Cannot Reproduce > java.util.ConcurrentModificationException while sending message > --

[jira] [Closed] (AMQ-3432) Slave broker able to start together with Master broker (shared file system master/slave setup)

[ https://issues.apache.org/jira/browse/AMQ-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3432. - Resolution: Incomplete > Slave broker able to start together with Master broker (shared file system > mast

[jira] [Closed] (AMQ-3240) load balance on a VirtualTopic queue broken where there are consumers subscribining to both the VT queue and VirtualTopic itself

[ https://issues.apache.org/jira/browse/AMQ-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3240. - Resolution: Cannot Reproduce > load balance on a VirtualTopic queue broken where there are consumers > sub

[jira] [Resolved] (AMQ-5323) ActiveMQ Message getProperty and setProperty inconsistent behaviour

[ https://issues.apache.org/jira/browse/AMQ-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5323. --- Resolution: Fixed Fix Version/s: 5.11.0 Fixed on trunk. > ActiveMQ Message getProperty and setP

[jira] [Updated] (AMQ-5323) ActiveMQ Message getProperty and setProperty inconsistent behaviour

[ https://issues.apache.org/jira/browse/AMQ-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5323: -- Priority: Trivial (was: Major) > ActiveMQ Message getProperty and setProperty inconsistent behaviour > -

[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=14098569#comment-14098569 ] Timothy Bish commented on AMQ-5322: --- You can configure the cache size in your Broker confi

[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 ] Timothy Bish updated AMQ-5322: -- Attachment: AMQ5322Test.java Test that passes using indicated scenario. > Message is assigned to diffe

[jira] [Updated] (AMQ-5323) ActiveMQ Message getProperty and setProperty inconsistent behaviour

[ https://issues.apache.org/jira/browse/AMQ-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joao Silva de Melo updated AMQ-5323: Description: When you retrieve the JMSDeliveryMode property from an ActiveMQ message, it ret

[jira] [Created] (AMQ-5323) ActiveMQ Message getProperty and setProperty inconsistent behaviour

Joao Silva de Melo created AMQ-5323: --- Summary: ActiveMQ Message getProperty and setProperty inconsistent behaviour Key: AMQ-5323 URL: https://issues.apache.org/jira/browse/AMQ-5323 Project: ActiveMQ

Jenkins build is unstable: ActiveMQ » ActiveMQ :: Runtime Configuration #1506

See

Jenkins build is back to normal : ActiveMQ » ActiveMQ :: MQTT Protocol #1506

See

Jenkins build is back to normal : ActiveMQ » ActiveMQ :: KahaDB Store #1506

See

Jenkins build is unstable: ActiveMQ » ActiveMQ :: RA #1506

See

Jenkins build is unstable: ActiveMQ » ActiveMQ :: Web #1506

See

Jenkins build is unstable: ActiveMQ » ActiveMQ :: STOMP Protocol #1506

See

Single topic vs multiple topic scaling strategies

Hi, Imagine lots of devices sending messages to a broker. It would be better strategy to scale with a single topic with all the messages from all devices. Or in contrast it would be better to scale with lots of topics (one per device containing only the messages from that device) ? What is your