Exclusive Consumers

Proposed small change to org.apache.activemq.broker.region.Queue addSubscription() method: If the new consumer is exclusive and has the maximum priority (127), replace the existing exclusive consumer even if it also has a priority of 127 as follows (line 385 in version 5.4.2 source): if (exclusiv

[jira] Issue Comment Edited: (AMQNET-318) Add support for an "all" prefetch policy setting

[ https://issues.apache.org/jira/browse/AMQNET-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005757#comment-13005757 ] Jim Gomes edited comment on AMQNET-318 at 3/11/11 8:46 PM: --- Look

How to connect to ActiveMQ from Android

Hi, I am trying to connect to an ActiveMQ broker from Android, but have not had any luck so far. When I try to include the activemq-all-5.4.3.jar into the android project, it fails to compile. (Locks up and freezes the system). Not sure what is going on here. I don't mind connecting through some

[jira] Commented: (AMQNET-318) Add support for an "all" prefetch policy setting

[ https://issues.apache.org/jira/browse/AMQNET-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005757#comment-13005757 ] Jim Gomes commented on AMQNET-318: -- Looks like there is away of doing what I was asking f

[jira] Commented: (AMQNET-318) Add support for an "all" prefetch policy setting

[ https://issues.apache.org/jira/browse/AMQNET-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005744#comment-13005744 ] Timothy Bish commented on AMQNET-318: - as part of this or maybe in addition we might w

[jira] Created: (AMQNET-318) Add support for an "all" prefetch policy setting

Add support for an "all" prefetch policy setting Key: AMQNET-318 URL: https://issues.apache.org/jira/browse/AMQNET-318 Project: ActiveMQ .Net Issue Type: Improvement Components: Acti

[jira] Commented: (AMQNET-317) Throw Exception while close connection

[ https://issues.apache.org/jira/browse/AMQNET-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005736#comment-13005736 ] Jim Gomes commented on AMQNET-317: -- I would suggest using the failover protocol in this s

Re: activemq fails to start on RedHat linux

Found the problem. This version has updated command (http://activemq.apache.org/unix-shell-script.html) following command worked: bin/activemq start -- View this message in context: http://activemq.2283324.n4.nabble.com/activemq-fails-to-start-on-RedHat-linux-tp3344481p3348617.html Sent from the

[jira] Created: (AMQ-3216) kahadb should be set optional in manifest file

kahadb should be set optional in manifest file -- Key: AMQ-3216 URL: https://issues.apache.org/jira/browse/AMQ-3216 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Ve

[jira] Updated: (AMQ-3215) Drop-down list to move messages from one queue to another is not wide enough to show complete queue names

[ https://issues.apache.org/jira/browse/AMQ-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Allain updated AMQ-3215: - Attachment: screenshot-1.jpg > Drop-down list to move messages from one queue to another is not wide enough

[jira] Updated: (AMQ-1612) Publishing to a deleted destination topic does not produce any errors

[ https://issues.apache.org/jira/browse/AMQ-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Koltzau updated AMQ-1612: --- Attachment: DeleteDestTest.java This issue occurs with both topics and queues. What I am testing: 1. Cr

[jira] Commented: (AMQ-3215) Drop-down list to move messages from one queue to another is not wide enough to show complete queue names

[ https://issues.apache.org/jira/browse/AMQ-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005681#comment-13005681 ] Carl Allain commented on AMQ-3215: -- We're talning about the Admin Console of course. > Dro

[jira] Created: (AMQ-3215) Drop-down list to move messages from one queue to another is not wide enough to show complete queue names

Drop-down list to move messages from one queue to another is not wide enough to show complete queue names - Key: AMQ-3215 URL: https://issues.apache.org/jira/b

Build failed in Jenkins: ActiveMQ #598

See Changes: [gtully] https://issues.apache.org/jira/browse/AMQ-3183 - fix typo in useAuthenticatedPrincipalForJMSXUserID -- [...truncated 3959 lines...] AU activemq-ra/src/main/java/org/

[jira] Issue Comment Edited: (AMQ-3211) JMSXUserId Can be spoofed by client

[ https://issues.apache.org/jira/browse/AMQ-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005593#comment-13005593 ] Gary Tully edited comment on AMQ-3211 at 3/11/11 11:07 AM: --- there

[jira] Commented: (AMQ-3183) Set JMSXUserID value based on authenticated principal

[ https://issues.apache.org/jira/browse/AMQ-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005594#comment-13005594 ] Gary Tully commented on AMQ-3183: - Attribute typo, useAuthenticatedPrincipalForJMXUserID is