Jenkins build became unstable: ActiveMQ » ActiveMQ :: LevelDB Store #1504

See

Build failed in Jenkins: ActiveMQ » ActiveMQ :: MQTT Protocol #1504

See Changes: [tabish121] https://issues.apache.org/jira/browse/AMQ-5290 -- [02:02:35] [INFO]

Build failed in Jenkins: ActiveMQ #1504

See Changes: [tabish121] https://issues.apache.org/jira/browse/AMQ-5290 -- [...truncated 1953 lines...] Took 0.18 sec [JENKINS] Archiving

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

See Changes: [tabish121] https://issues.apache.org/jira/browse/AMQ-5290 -- [INFO]

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

See Changes: [tabish121] https://issues.apache.org/jira/browse/AMQ-5290 -- [...truncated 9587 lines...] Took 35 ms [JENKINS] Archiving

[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS

[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094851#comment-14094851 ] Jim Gomes commented on AMQNET-454: -- I refactored Patch 27 to preserve the standard nant-c

[jira] [Closed] (AMQ-5250) temp queue not working after long run of activemq

[ https://issues.apache.org/jira/browse/AMQ-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5250. - Resolution: Cannot Reproduce No test case to investigate and from the description it sounds like normal tem

Re: DFSR and ActiveMQ on Windows (Distributed File System Replication)

Any suggestions on this end ? -- View this message in context: http://activemq.2283324.n4.nabble.com/DFSR-and-ActiveMQ-on-Windows-Distributed-File-System-Replication-tp4684285p4684482.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Commented] (AMQ-4652) Test failed under Java 8

[ https://issues.apache.org/jira/browse/AMQ-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094597#comment-14094597 ] Timothy Bish commented on AMQ-4652: --- I think we can close this one now, the tests under Ja

[jira] [Commented] (AMQ-5290) MQTT clients using durable subscriptions on networked brokers received duplicates

[ https://issues.apache.org/jira/browse/AMQ-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094516#comment-14094516 ] Timothy Bish commented on AMQ-5290: --- Cleaned up a little and shortened the transport optio

[jira] [Resolved] (AMQ-5290) MQTT clients using durable subscriptions on networked brokers received duplicates

[ https://issues.apache.org/jira/browse/AMQ-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5290. --- Resolution: Fixed Assignee: Timothy Bish Implemented an initial solution which is to use a strate

[jira] [Comment Edited] (AMQ-5290) MQTT clients using durable subscriptions on networked brokers received duplicates

[ https://issues.apache.org/jira/browse/AMQ-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088318#comment-14088318 ] Timothy Bish edited comment on AMQ-5290 at 8/12/14 7:00 PM: Adde

[jira] [Resolved] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

[ https://issues.apache.org/jira/browse/AMQNET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-488. - Resolution: Fixed Assignee: Timothy Bish (was: Jim Gomes) Fixed > Deadlock in InactivityM

[jira] [Updated] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

[ https://issues.apache.org/jira/browse/AMQNET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-488: Fix Version/s: 1.7.0 > Deadlock in InactivityMonitor when using Failover >

[jira] [Updated] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

[ https://issues.apache.org/jira/browse/AMQNET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-488: Affects Version/s: 1.6.3 > Deadlock in InactivityMonitor when using Failover >

[jira] [Updated] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

[ https://issues.apache.org/jira/browse/AMQNET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-488: Fix Version/s: 1.6.4 > Deadlock in InactivityMonitor when using Failover >

[jira] [Commented] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

[ https://issues.apache.org/jira/browse/AMQNET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094380#comment-14094380 ] Timothy Bish commented on AMQNET-488: - Reviewed and tested, looks good. Patch applied

[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS

[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094223#comment-14094223 ] Timothy Bish commented on AMQNET-454: - Patches applied. > Add Apache Qpid provider to

[jira] [Updated] (AMQNET-454) Add Apache Qpid provider to NMS

[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated AMQNET-454: --- Attachment: Apache.NMS.AMQP-28-close-qpid-sender-receiver.patch Patch 28 closes the underlying qpid s

[jira] [Updated] (AMQNET-454) Add Apache Qpid provider to NMS

[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated AMQNET-454: --- Attachment: Apache.NMS.AMQP-27-nant-unmanaged-copy.patch Patch 27 includes copying unmanaged content

[jira] [Commented] (AMQ-5174) Cannot use the JDBCIOExceptionHandler when kahadb is configured with lease-database-locker

[ https://issues.apache.org/jira/browse/AMQ-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094172#comment-14094172 ] Kevin commented on AMQ-5174: is there any timeline that the activeMQ 5.11.0 released? it is fi

[jira] [Updated] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

[ https://issues.apache.org/jira/browse/AMQNET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurence Pike updated AMQNET-488: - Attachment: AMQNET-488-CompositeTaskRunner.cs.patch AMQNET-488-CompositeTaskRunner

[jira] [Created] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

Laurence Pike created AMQNET-488: Summary: Deadlock in InactivityMonitor when using Failover Key: AMQNET-488 URL: https://issues.apache.org/jira/browse/AMQNET-488 Project: ActiveMQ .Net Issue

Jenkins build became unstable: ActiveMQ » ActiveMQ :: Web Demo #1503

See

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: Web #1503

See

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

See

[jira] [Resolved] (AMQ-5304) groupClass not applied to TempDestinationAuthorizationEntry

[ https://issues.apache.org/jira/browse/AMQ-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke resolved AMQ-5304. - Resolution: Fixed Fix Version/s: 5.11.0 > groupClass not applied to TempDestinationAuthoriza

[jira] [Commented] (AMQ-5304) groupClass not applied to TempDestinationAuthorizationEntry

[ https://issues.apache.org/jira/browse/AMQ-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093858#comment-14093858 ] Torsten Mielke commented on AMQ-5304: - Fixed in commit [ec2a3c750bbfb33763ac56b8b0a660b