Build failed in Jenkins: ActiveMQ #1444

See Changes: [gtully] remove exclude of deleted test [tabish121] Adds a test for anonymous Producers [gtully] https://issues.apache.org/jira/browse/AMQ-5087 fix and test [dejan] https://issues.apache.org/jira/browse/AMQ-5090 - improve failo

Jenkins build is unstable: ActiveMQ » ActiveMQ :: AMQP #1444

See

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

See

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

See Changes: [gtully] https://issues.apache.org/jira/browse/AMQ-5087 fix and test [hadrian] [minor] Use MemoryPersistenceAdapter for testing when choice of persistence adapter is indifferent

[jira] [Updated] (AMQ-5092) MQTT uses duplicate packet IDs for PUBLISH messages

[ https://issues.apache.org/jira/browse/AMQ-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhiraj Bokde updated AMQ-5092: -- Attachment: AMQ-5092.patch Patch to fix MQTT publish packet id generation > MQTT uses duplicate packet I

[jira] [Created] (AMQ-5092) MQTT uses duplicate packet IDs for PUBLISH messages

Dhiraj Bokde created AMQ-5092: - Summary: MQTT uses duplicate packet IDs for PUBLISH messages Key: AMQ-5092 URL: https://issues.apache.org/jira/browse/AMQ-5092 Project: ActiveMQ Issue Type: Bug

Re: ActiveMQ 5.10 release date?

There are some 342 commits since 5.9.0. It's easy to get them running: $ git log 87c9bbebacfe1d2248b4a55d601f0b089d40b742..HEAD (where 87c9bbebacfe1d2248b4a55d601f0b089d40b742 is the 5.9.0 release tag) Because the resulting log is about 80k in size, I will not attach it here, but please find be

[VOTE RESULT] Release Apache Apollo 1.7 (Release Candidate 2)

I'm closing out this vote thread. The release vote passes with 6 +1s. Thank you all for taking the time to review the release. On Mon, Feb 24, 2014 at 9:05 PM, Hiram Chirino wrote: > Hi Everyone, > > I've deployed another 1.7 release candidate. This one should fix the > problems with the licen

Re: [jira] [Resolved] (AMQ-4328) Cross talk over duplex network connection can lead to blocking

Also, is this fix dependent on any other changes made in 5.9? Is it safe if we decide to apply the fix to the 5.8.0 version in isolation? -- View this message in context: http://activemq.2283324.n4.nabble.com/jira-Resolved-AMQ-4328-Cross-talk-over-duplex-network-connection-can-lead-to-blocking

[jira] [Resolved] (AMQ-5091) Upgrade to jolokia 1.2

[ https://issues.apache.org/jira/browse/AMQ-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved AMQ-5091. -- Resolution: Fixed > Upgrade to jolokia 1.2 > -- > > Key: AMQ-5091 >

[jira] [Commented] (AMQ-5091) Upgrade to jolokia 1.2

[ https://issues.apache.org/jira/browse/AMQ-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925709#comment-13925709 ] Claus Ibsen commented on AMQ-5091: -- The problem was using json-simple 1.1.1 from AMQ, and t

[jira] [Commented] (AMQ-5091) Upgrade to jolokia 1.2

[ https://issues.apache.org/jira/browse/AMQ-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925697#comment-13925697 ] Claus Ibsen commented on AMQ-5091: -- Hmm tried again and this time it worked {code} { timest

[jira] [Commented] (AMQ-5091) Upgrade to jolokia 1.2

[ https://issues.apache.org/jira/browse/AMQ-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925698#comment-13925698 ] Claus Ibsen commented on AMQ-5091: -- Accessing the url http://localhost:8161/api/jolokia >

[jira] [Commented] (AMQ-5091) Upgrade to jolokia 1.2

[ https://issues.apache.org/jira/browse/AMQ-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925691#comment-13925691 ] Claus Ibsen commented on AMQ-5091: -- ActiveMQ standalone has this problem with the 1.2 jolok

[jira] [Created] (AMQ-5091) Upgrade to jolokia 1.2

Claus Ibsen created AMQ-5091: Summary: Upgrade to jolokia 1.2 Key: AMQ-5091 URL: https://issues.apache.org/jira/browse/AMQ-5091 Project: ActiveMQ Issue Type: Improvement Components: Bro

[jira] [Updated] (AMQNET-471) Synchronous message consumer will lose a message that failed to commit whilst the broker was unavailable

[ https://issues.apache.org/jira/browse/AMQNET-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imran updated AMQNET-471: - Description: If the broker is down then the client can not commit the current message. An exception is thrown by

[jira] [Commented] (AMQNET-471) Synchronous message consumer will lose a message that failed to commit whilst the broker was unavailable

[ https://issues.apache.org/jira/browse/AMQNET-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925669#comment-13925669 ] Imran commented on AMQNET-471: -- I rewrote the test in java using an active mq 5.9 client. It

[jira] [Commented] (AMQNET-338) TcpTransport.cs - Close() taking 30 seconds

[ https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925508#comment-13925508 ] Jim Gomes commented on AMQNET-338: -- Look at the changes I checked in. It should show the