[jira] [Commented] (AMQ-5112) MQTT server connections are not thread safe

[ https://issues.apache.org/jira/browse/AMQ-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13942950#comment-13942950 ] Dejan Bosanac commented on AMQ-5112: Thanks Dhiraj, I applied the patch and also

[jira] [Created] (AMQ-5114) AbortSlowAckConsumerStrategy with abortConnection=false; ensure consumers are always removed from the broker

Gary Tully created AMQ-5114: --- Summary: AbortSlowAckConsumerStrategy with abortConnection=false; ensure consumers are always removed from the broker Key: AMQ-5114 URL: https://issues.apache.org/jira/browse/AMQ-5114

[jira] [Resolved] (AMQ-5114) AbortSlowAckConsumerStrategy with abortConnection=false; ensure consumers are always removed from the broker

[ https://issues.apache.org/jira/browse/AMQ-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-5114. - Resolution: Fixed fix and test in http://git-wip-us.apache.org/repos/asf/activemq/commit/9bf9e1c0

[jira] [Resolved] (AMQ-4533) Messages stuck in queue with redelivered=true

[ https://issues.apache.org/jira/browse/AMQ-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-4533. - Resolution: Fixed Using abortConnection=false is viable with

[jira] [Assigned] (AMQ-5068) Support hardening/persisting the JMSRedeliveryFlag across restarts

[ https://issues.apache.org/jira/browse/AMQ-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned AMQ-5068: --- Assignee: Gary Tully Support hardening/persisting the JMSRedeliveryFlag across restarts

[jira] [Commented] (AMQ-5115) LevelDB sync=true is not being honored.

[ https://issues.apache.org/jira/browse/AMQ-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943205#comment-13943205 ] Hiram Chirino commented on AMQ-5115: This could potential lead to data loss as writes to

[jira] [Created] (AMQ-5115) LevelDB sync=true is not being honored.

Hiram Chirino created AMQ-5115: -- Summary: LevelDB sync=true is not being honored. Key: AMQ-5115 URL: https://issues.apache.org/jira/browse/AMQ-5115 Project: ActiveMQ Issue Type: Bug

[jira] [Created] (AMQ-5116) batchStatment is misspelled for JDBC adaptors

Jeff Genender created AMQ-5116: -- Summary: batchStatment is misspelled for JDBC adaptors Key: AMQ-5116 URL: https://issues.apache.org/jira/browse/AMQ-5116 Project: ActiveMQ Issue Type: Bug

[GitHub] activemq pull request: Fix for AMQ-5116. Deprecated batchStatment ...

GitHub user jgenender opened a pull request: https://github.com/apache/activemq/pull/18 Fix for AMQ-5116. Deprecated batchStatment and added batchStatement. Added deprecation warnings in the log for those using the misspelled version. Both versions will set batchStatement for

[jira] [Commented] (AMQ-5116) batchStatment is misspelled for JDBC adaptors

[ https://issues.apache.org/jira/browse/AMQ-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943257#comment-13943257 ] Jeff Genender commented on AMQ-5116: Pull request sent. batchStatment is misspelled

[jira] [Commented] (AMQ-5116) batchStatment is misspelled for JDBC adaptors

[ https://issues.apache.org/jira/browse/AMQ-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943254#comment-13943254 ] ASF GitHub Bot commented on AMQ-5116: - GitHub user jgenender opened a pull request:

[jira] [Updated] (AMQ-5116) batchStatment is misspelled for JDBC adaptors

[ https://issues.apache.org/jira/browse/AMQ-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Genender updated AMQ-5116: --- Attachment: patch Attaching a patch as the github delay may be a bit slow in getting the latest

[jira] [Commented] (AMQ-5116) batchStatment is misspelled for JDBC adaptors

[ https://issues.apache.org/jira/browse/AMQ-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943364#comment-13943364 ] ASF GitHub Bot commented on AMQ-5116: - Github user asfgit closed the pull request at:

[jira] [Resolved] (AMQ-5116) batchStatment is misspelled for JDBC adaptors

[ https://issues.apache.org/jira/browse/AMQ-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino resolved AMQ-5116. Resolution: Fixed Fix Version/s: 5.10.0 Assignee: Hiram Chirino batchStatment is

[jira] [Reopened] (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 reopened AMQ-5092: --- Packet id generation must resume id sequence after client reconnects MQTT uses duplicate packet IDs for

[jira] [Commented] (AMQ-4884) Wildcard matches do not match

[ https://issues.apache.org/jira/browse/AMQ-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943474#comment-13943474 ] Dhiraj Bokde commented on AMQ-4884: --- With the MQTT path fix in AMQ-5074, we can mark this

[jira] [Resolved] (AMQ-4884) Wildcard matches do not match

[ https://issues.apache.org/jira/browse/AMQ-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-4884. --- Resolution: Fixed Wildcard matches do not match - Key:

[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.patch3 Attaching patch3 to fix packet id generation, resolves resendMessageId()

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13943550#comment-13943550 ] Timothy Bish commented on AMQ-5092: --- patch applied on trunk with thanks. Tests are all