Jenkins build became unstable: ActiveMQ » ActiveMQ :: RA #1458

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-ra/1458/

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: LevelDB Store #1458

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-leveldb-store/1458/

Build failed in Jenkins: ActiveMQ » ActiveMQ :: Unit Tests #1458

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-unit-tests/1458/changes Changes: [tabish121] https://issues.apache.org/jira/browse/AMQ-5086 -- [...truncated 815 lines...] [06:32:49] Tests run: 2, Failures: 0, Errors: 0, Skipped:

Jenkins build became unstable: ActiveMQ » ActiveMQ :: MQTT Protocol #1458

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-mqtt/1458/

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: Runtime Configuration #1458

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-runtime-config/1458/

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: AMQP #1458

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-amqp/1458/

[jira] [Created] (AMQ-5220) Advisory messages are still empty when received with a Stomp subscription

Vladislav Krakhalev created AMQ-5220: Summary: Advisory messages are still empty when received with a Stomp subscription Key: AMQ-5220 URL: https://issues.apache.org/jira/browse/AMQ-5220 Project:

[jira] [Reopened] (AMQ-4277) activemq-web - REST GET 204

[ https://issues.apache.org/jira/browse/AMQ-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac reopened AMQ-4277: Let's examine this issue again activemq-web - REST GET 204 ---

[jira] [Updated] (AMQ-4277) activemq-web - REST GET 204

[ https://issues.apache.org/jira/browse/AMQ-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac updated AMQ-4277: --- Fix Version/s: (was: 5.10.0) 5.11.0 activemq-web - REST GET 204

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

I reopened the issue and mark it for 5.11. I don’t think this issue is a blocker for this release. Having said that, the vote was open for 5 days with not -1s, so I’ll close it now and continue with the release. Regards -- Dejan Bosanac -- Red Hat, Inc. FuseSource is now part

[RESULT][VOTE] Apache ActiveMQ 5.10.0

Vote passes with 8 +1 votes (Dejan, Tim, Claus, Hadrian, Gary, Hiram, Jim, Christian) and no other votes. I will proceed to publish the artifacts and complete the release. Thanks to all who took the time to test the artifacts and vote. Regards -- Dejan Bosanac -- Red Hat,

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

I didn't really get an answer to my earlier post regarding AMQ-5174. Can that be included in ActiveMQ 5.10 too? Thanks, Paul On Tue, Jun 10, 2014 at 7:04 AM, Dejan Bosanac de...@nighttale.net wrote: I reopened the issue and mark it for 5.11. I don’t think this issue is a blocker for this

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

Hi Paul, it’s a new feature request and there’s no work being done on it, so it’s not something that should block the release. If you can create a patch for this, it’d speed up the inclusion of it for the future. Contributions are always more than welcomed. Regards -- Dejan Bosanac

[ANNOUNCE] Apache ActiveMQ 5.10.0

The Apache ActiveMQ team is proud to announce the release of Apache ActiveMQ 5.10.0. This release addresses over 200 issues and introduces many improvements particularly in MQTT and AMQP support. Full details and download link can be found in the release page:

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

See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/960/changes Changes: [gtully] remove duplicate slf4j-log4j12 dep b/c it is in activemq-all from https://issues.apache.org/jira/browse/AMQ-3715 -- [...truncated 11959 lines...] [JENKINS] Archiving

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: Assembly #960

See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$apache-activemq/960/ -- [INFO] [INFO]

[jira] [Commented] (AMQ-3883) activemq-jaas authorization doesn't work with Karaf JAAS LoginModule

[ https://issues.apache.org/jira/browse/AMQ-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027196#comment-14027196 ] Chris Schultz commented on AMQ-3883: I have review the code for LDAP Authorisation

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

Thanks Dejan and Tim - I agree this jira entry should not hold up the release. -- View this message in context: http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-Candidate-2-tp4681721p4681994.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

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

[ https://issues.apache.org/jira/browse/AMQ-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027280#comment-14027280 ] Chad Kelly commented on AMQ-5155: - Someone please help resolve this ticket. The bug

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

+1 (non-binding) I was hoping to briefly review all of the jira entires, but only managed about 50 of them. I will try to do more - as life permits. -- View this message in context: http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-Candidate-2-tp4681721p4681995.html

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

[ https://issues.apache.org/jira/browse/AMQ-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027304#comment-14027304 ] Timothy Bish commented on AMQ-5155: --- Why not try and create a unit test and submit a patch

[jira] [Commented] (AMQ-4893) UTF8Buffer should be a valid object for setObjectProperty

[ https://issues.apache.org/jira/browse/AMQ-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027302#comment-14027302 ] Arthur Naseef commented on AMQ-4893: Fix revision:

[jira] [Commented] (AMQ-4892) MQTT clients disconnecting due to socket error do not publish the configured last will and testament message.

[ https://issues.apache.org/jira/browse/AMQ-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027305#comment-14027305 ] Arthur Naseef commented on AMQ-4892: Fix revision:

[jira] [Commented] (AMQ-4883) Fusesource release repo not needed

[ https://issues.apache.org/jira/browse/AMQ-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027308#comment-14027308 ] Arthur Naseef commented on AMQ-4883: Fix revision:

[jira] [Commented] (AMQ-4970) Deletion of a queue inaffective across broker restart

[ https://issues.apache.org/jira/browse/AMQ-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027309#comment-14027309 ] Arthur Naseef commented on AMQ-4970: Fix revision:

[jira] [Commented] (AMQ-4857) WSServlet.doWebSocketConnect throws NPE if called with null protocol

[ https://issues.apache.org/jira/browse/AMQ-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027307#comment-14027307 ] Arthur Naseef commented on AMQ-4857: Fix revision:

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

Hi Arthur Instead of adding a comment to each jira ticket about the commit. You can get JIRA to link to it automatic when you click the source sub tab. But that requires AFAIR to tell JIRA to do that, and where the source code is. Maybe INFRA can help with that. On Wed, Jun 11, 2014 at 3:04 AM,