Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: MQTT Protocol #939

See -- [INFO] [INFO] --

[GitHub] activemq pull request: Add Jetty host property to resolve URL mess...

GitHub user jsherman1 opened a pull request: https://github.com/apache/activemq/pull/23 Add Jetty host property to resolve URL message You can merge this pull request into a Git repository by running: $ git pull https://github.com/jsherman1/activemq jetty-host Alternatively y

[jira] [Created] (AMQ-5178) ActiveMQ Karaf - Add CLI command to create queue/topic

Claus Ibsen created AMQ-5178: Summary: ActiveMQ Karaf - Add CLI command to create queue/topic Key: AMQ-5178 URL: https://issues.apache.org/jira/browse/AMQ-5178 Project: ActiveMQ Issue Type: New F

[jira] [Commented] (AMQ-5160) Wildcard subscriptions bypass Authentication / Authorization

[ https://issues.apache.org/jira/browse/AMQ-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13992602#comment-13992602 ] Surf commented on AMQ-5160: --- [~dhirajsb] Thanks..I rebuilt whole project and it worked ! On the o

Re: Send headers with ActiveMQ ajax client

Looking at the code, I see the missing linkage in _amq.js in the _sendMessage() function. The servlet will attach all request parameters as message properties (aka headers). But, that method does not attach any parameters. Note that message is called by the sendMessage() function. BTW - what ve

Re: AMQP 1.0 connection property names

On Tue, May 13, 2014 at 12:31 PM, Gordon Sim wrote: > > My only comment around the actual names is that 'process' doesnt >> immediately make me think 'name' and even seems a little like it could be >> describing the same thing as 'pid' if you didnt know both properties >> existed, which I have alw

Re: AMQP 1.0 connection property names

Sounds like a good idea to me. I have been meaning to do the same thing with some other properties like 'version' and 'product'. My only comment around the actual names is that 'process' doesnt immediately make me think 'name' and even seems a little like it could be describing the same thing as '

Re: AMQP 1.0 connection property names

+1 Ship It! - Original Message - > From: "Gordon Sim" > To: us...@qpid.apache.org > Cc: dev@activemq.apache.org > Sent: Wednesday, May 14, 2014 12:54:43 PM > Subject: Re: AMQP 1.0 connection property names > > On 05/13/2014 08:25 PM, Robbie Gemmell wrote: > > On 13 May 2014 17:59, Justin

[jira] [Commented] (AMQ-5160) Wildcard subscriptions bypass Authentication / Authorization

[ https://issues.apache.org/jira/browse/AMQ-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13992838#comment-13992838 ] Dhiraj Bokde commented on AMQ-5160: --- Hi [~surfnerd], sorry about that, I missed the fact t

[jira] [Resolved] (AMQ-5183) Switch to using Proton's Event logic for detecting AMQP state changes

[ https://issues.apache.org/jira/browse/AMQ-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5183. --- Resolution: Fixed implemented on trunk > Switch to using Proton's Event logic for detecting AMQP state

Re: Compiling with Java 8

That sounds like a good plan. Agree with Claus on not targetting 5.10. -- View this message in context: http://activemq.2283324.n4.nabble.com/Compiling-with-Java-8-tp4680938p4680980.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

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

Paddy created AMQ-5185: -- Summary: Duplicate messages occur for MQTT cleanSession=false client with network of brokers Key: AMQ-5185 URL: https://issues.apache.org/jira/browse/AMQ-5185 Project: ActiveMQ

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

Christian Mamen created AMQCPP-543: -- Summary: message producer send never blocking when using producer flow control Key: AMQCPP-543 URL: https://issues.apache.org/jira/browse/AMQCPP-543 Project: Acti