[jira] [Commented] (AMQ-5379) AMQP - allow setting prefetch size

[ https://issues.apache.org/jira/browse/AMQ-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234150#comment-14234150 ] Dejan Bosanac commented on AMQ-5379: I pushed the change that sets zero prefetch when

[jira] [Assigned] (AMQ-5438) Archiving mKahaDB log files cause broker restart

[ https://issues.apache.org/jira/browse/AMQ-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac reassigned AMQ-5438: -- Assignee: Dejan Bosanac Archiving mKahaDB log files cause broker restart

Jenkins build became unstable: ActiveMQ » ActiveMQ :: AMQP #1560

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

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: STOMP Protocol #1559

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-stomp/1559/

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: RA #1559

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

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

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

[GitHub] activemq pull request: Fixed AMQ-5438. Added code to create KahaDB...

Github user asfgit closed the pull request at: https://github.com/apache/activemq/pull/50 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (AMQ-5438) Archiving mKahaDB log files cause broker restart

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

[jira] [Resolved] (AMQ-5438) Archiving mKahaDB log files cause broker restart

[ https://issues.apache.org/jira/browse/AMQ-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5438. Resolution: Fixed Fix Version/s: 5.11.0 Patch applied. Thanks! Archiving mKahaDB log files

[GitHub] activemq-6 pull request: ACTIVEMQ6-11 - fix distribution build for...

Github user asfgit closed the pull request at: https://github.com/apache/activemq-6/pull/31 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (ACTIVEMQ6-11) Fix the distribution build

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

[jira] [Created] (AMQ-5475) AMQP transport does not send correct response to unsupported clients

Timothy Bish created AMQ-5475: - Summary: AMQP transport does not send correct response to unsupported clients Key: AMQ-5475 URL: https://issues.apache.org/jira/browse/AMQ-5475 Project: ActiveMQ

[jira] [Commented] (ACTIVEMQ6-36) Disallow use of SSLv3 to protect against POODLE

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234311#comment-14234311 ] Torsten Mielke commented on ACTIVEMQ6-36: - Using this configuration should

[jira] [Commented] (AMQ-5342) Deadlock in network of brokers simple architecture

[ https://issues.apache.org/jira/browse/AMQ-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234639#comment-14234639 ] Tim Bain commented on AMQ-5342: --- Is there a reason that you've got two duplex connections

[jira] [Commented] (AMQ-5338) Run into Memory Leak problem after upgrade from 5.5.1 to 5.10

[ https://issues.apache.org/jira/browse/AMQ-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234645#comment-14234645 ] Tim Bain commented on AMQ-5338: --- What GC strategy are you using? And which JVM

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

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

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

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

[jira] [Updated] (AMQ-5473) Race condition caused by Linkstealing might make durable subs inactive

[ https://issues.apache.org/jira/browse/AMQ-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AR updated AMQ-5473: Attachment: (was: linksteal_durablesub.patch) Race condition caused by Linkstealing might make durable subs inactive

[jira] [Updated] (AMQ-5473) Race condition caused by Linkstealing might make durable subs inactive

[ https://issues.apache.org/jira/browse/AMQ-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AR updated AMQ-5473: Attachment: linksteal_durablesub.patch patch updated. Race condition caused by Linkstealing might make durable subs

[jira] [Closed] (ACTIVEMQ6-42) Fix FORCED_DELIVERY_MESSAGE dependent on hornetq naming

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ACTIVEMQ6-42. Resolution: Won't Fix Fix Version/s: (was: 6.0.0) Fix FORCED_DELIVERY_MESSAGE

[jira] [Reopened] (ACTIVEMQ6-42) Fix FORCED_DELIVERY_MESSAGE dependent on hornetq naming

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ACTIVEMQ6-42: -- Fix FORCED_DELIVERY_MESSAGE dependent on hornetq naming