[jira] [Updated] (ARTEMIS-2193) Artemis fails on OutOfMemoryError with fast producers

[ https://issues.apache.org/jira/browse/ARTEMIS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Kaczkowski updated ARTEMIS-2193: --- Description: The broker fails on OOM Error in a couple of hours of testing with

[jira] [Updated] (ARTEMIS-2193) Artemis fails on OutOfMemoryError with fast producers

[ https://issues.apache.org/jira/browse/ARTEMIS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Kaczkowski updated ARTEMIS-2193: --- Description: The broker fails on OOM Error in a couple of hours of testing (2-10h)

[jira] [Updated] (ARTEMIS-2193) Artemis fails on OutOfMemoryError with fast producers

[ https://issues.apache.org/jira/browse/ARTEMIS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Kaczkowski updated ARTEMIS-2193: --- Description: The broker fails on OOM Error in a couple of hours of testing with

[jira] [Updated] (ARTEMIS-2193) Artemis fails on OutOfMemoryError with fast producers

[ https://issues.apache.org/jira/browse/ARTEMIS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Kaczkowski updated ARTEMIS-2193: --- Description: The broker fails on OOM Error in a couple of hours of testing with

[jira] [Updated] (ARTEMIS-2193) Artemis fails on OutOfMemoryError with fast producers

[ https://issues.apache.org/jira/browse/ARTEMIS-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Kaczkowski updated ARTEMIS-2193: --- Description: The broker fails on OOM Error in a couple of hours of testing with

[jira] [Commented] (AMQCPP-619) Support for SSL wilcard certificate

[ https://issues.apache.org/jira/browse/AMQCPP-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709562#comment-16709562 ] Alvin Lin commented on AMQCPP-619: -- Would it be possible to to get this one in? AmazonMQ uses wildcard

[jira] [Commented] (ARTEMIS-2189) Allow deleting temporary destination when originating session is closed

[ https://issues.apache.org/jira/browse/ARTEMIS-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709542#comment-16709542 ] ASF GitHub Bot commented on ARTEMIS-2189: - Github user jbertram commented on a diff in the pull

[jira] [Commented] (AMQCPP-625) Inactivity mointor core dump

[ https://issues.apache.org/jira/browse/AMQCPP-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709488#comment-16709488 ] sapling commented on AMQCPP-625: fortest > Inactivity mointor core dump > -

[jira] [Issue Comment Deleted] (AMQCPP-625) Inactivity mointor core dump

[ https://issues.apache.org/jira/browse/AMQCPP-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sapling updated AMQCPP-625: --- Comment: was deleted (was: fortest) > Inactivity mointor core dump > - > >

[jira] [Commented] (ARTEMIS-2191) Makes PostOfficeImpl::route common paths inlineable

[ https://issues.apache.org/jira/browse/ARTEMIS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709404#comment-16709404 ] ASF GitHub Bot commented on ARTEMIS-2191: - Github user clebertsuconic commented on the issue:

[jira] [Commented] (ARTEMIS-2170) Optimized CoreMessage's checkProperties and cleanupInternalProperties methods

[ https://issues.apache.org/jira/browse/ARTEMIS-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709367#comment-16709367 ] ASF GitHub Bot commented on ARTEMIS-2170: - Github user michaelandrepearce commented on a diff

[jira] [Updated] (ARTEMIS-2192) LegacyLDAPSecuritySettingPlugin uses hard-coded RDN types

[ https://issues.apache.org/jira/browse/ARTEMIS-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-2192: Summary: LegacyLDAPSecuritySettingPlugin uses hard-coded RDN types (was:

[jira] [Commented] (ARTEMIS-2192) LegacyLDAPSecuritySettingPlugin uses hard-coded RDN types

[ https://issues.apache.org/jira/browse/ARTEMIS-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709260#comment-16709260 ] ASF GitHub Bot commented on ARTEMIS-2192: - GitHub user jbertram opened a pull request:

[jira] [Created] (ARTEMIS-2192) LegacyLDAPSecuritySettingPluginTest uses hard-coded RDN types

Justin Bertram created ARTEMIS-2192: --- Summary: LegacyLDAPSecuritySettingPluginTest uses hard-coded RDN types Key: ARTEMIS-2192 URL: https://issues.apache.org/jira/browse/ARTEMIS-2192 Project:

[jira] [Commented] (ARTEMIS-2189) Allow deleting temporary destination when originating session is closed

[ https://issues.apache.org/jira/browse/ARTEMIS-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709082#comment-16709082 ] ASF GitHub Bot commented on ARTEMIS-2189: - Github user tabish121 commented on a diff in the

[jira] [Commented] (ARTEMIS-2190) Core JMS client leaks temporary destination names

[ https://issues.apache.org/jira/browse/ARTEMIS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709052#comment-16709052 ] ASF GitHub Bot commented on ARTEMIS-2190: - GitHub user jbertram opened a pull request:

[jira] [Commented] (ARTEMIS-2191) Makes PostOfficeImpl::route common paths inlineable

[ https://issues.apache.org/jira/browse/ARTEMIS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709031#comment-16709031 ] ASF GitHub Bot commented on ARTEMIS-2191: - Github user franz1981 commented on the issue:

[jira] [Commented] (ARTEMIS-2191) Makes PostOfficeImpl::route common paths inlineable

[ https://issues.apache.org/jira/browse/ARTEMIS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709026#comment-16709026 ] ASF GitHub Bot commented on ARTEMIS-2191: - GitHub user franz1981 opened a pull request:

[jira] [Created] (ARTEMIS-2191) Makes PostOfficeImpl::route common paths inlineable

Francesco Nigro created ARTEMIS-2191: Summary: Makes PostOfficeImpl::route common paths inlineable Key: ARTEMIS-2191 URL: https://issues.apache.org/jira/browse/ARTEMIS-2191 Project: ActiveMQ

[jira] [Commented] (AMQ-7097) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases

[ https://issues.apache.org/jira/browse/AMQ-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708992#comment-16708992 ] ASF subversion and git services commented on AMQ-7097: -- Commit

[jira] [Updated] (ARTEMIS-2190) Core JMS client leaks temporary destination names

[ https://issues.apache.org/jira/browse/ARTEMIS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-2190: Summary: Core JMS client leaks temporary destination names (was: Broker leaks temporary

[jira] [Updated] (ARTEMIS-2190) Broker leaks temporary destination names

[ https://issues.apache.org/jira/browse/ARTEMIS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-2190: Description: The core JMS client leaks the {{SimpleString}} identifiers for temporary

[jira] [Commented] (AMQ-7097) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases

[ https://issues.apache.org/jira/browse/AMQ-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708979#comment-16708979 ] ASF subversion and git services commented on AMQ-7097: -- Commit

[jira] [Updated] (ARTEMIS-2190) Broker leaks temporary destination names

[ https://issues.apache.org/jira/browse/ARTEMIS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-2190: Issue Type: Bug (was: New Feature) > Broker leaks temporary destination names >

[jira] [Updated] (ARTEMIS-2190) Broker leaks temporary destination names

[ https://issues.apache.org/jira/browse/ARTEMIS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-2190: Description: The core client has a small leak of temporary destinations. When a

[jira] [Updated] (ARTEMIS-2190) Broker leaks temporary destination names

[ https://issues.apache.org/jira/browse/ARTEMIS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Ross updated ARTEMIS-2190: -- Issue Type: Bug (was: New Feature) > Broker leaks temporary destination names >

[jira] [Assigned] (ARTEMIS-2190) Broker leaks temporary destination names

[ https://issues.apache.org/jira/browse/ARTEMIS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-2190: --- Assignee: Justin Bertram > Broker leaks temporary destination names >

[jira] [Updated] (ARTEMIS-2190) Broker leaks temporary destination names

[ https://issues.apache.org/jira/browse/ARTEMIS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-2190: Component/s: (was: Broker) > Broker leaks temporary destination names >

[jira] [Updated] (ARTEMIS-2190) Broker leaks temporary destination names

[ https://issues.apache.org/jira/browse/ARTEMIS-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Ross updated ARTEMIS-2190: -- Description: Broker has a small leak of temporary destination addresses. When temporary destination

[jira] [Created] (ARTEMIS-2190) Broker leaks temporary destination names

Tom Ross created ARTEMIS-2190: - Summary: Broker leaks temporary destination names Key: ARTEMIS-2190 URL: https://issues.apache.org/jira/browse/ARTEMIS-2190 Project: ActiveMQ Artemis Issue Type:

[jira] [Updated] (AMQ-7118) KahaDB store limit can be exceeded with durable subscribers.

[ https://issues.apache.org/jira/browse/AMQ-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jamie goodyear updated AMQ-7118: Fix Version/s: 5.16.0 > KahaDB store limit can be exceeded with durable subscribers. >

[jira] [Resolved] (AMQ-7118) KahaDB store limit can be exceeded with durable subscribers.

[ https://issues.apache.org/jira/browse/AMQ-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jamie goodyear resolved AMQ-7118. - Resolution: Fixed Thank you [~heathkesler] for the patch. > KahaDB store limit can be exceeded

[jira] [Commented] (AMQ-7118) KahaDB store limit can be exceeded with durable subscribers.

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

[jira] [Commented] (AMQ-7118) KahaDB store limit can be exceeded with durable subscribers.

[ https://issues.apache.org/jira/browse/AMQ-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708959#comment-16708959 ] ASF subversion and git services commented on AMQ-7118: -- Commit

[jira] [Commented] (AMQ-7118) KahaDB store limit can be exceeded with durable subscribers.

[ https://issues.apache.org/jira/browse/AMQ-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708949#comment-16708949 ] ASF subversion and git services commented on AMQ-7118: -- Commit

[jira] [Updated] (AMQ-7042) reduce number of retries when nonBlockingRedelivery is true

[ https://issues.apache.org/jira/browse/AMQ-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7042: -- Component/s: (was: Broker) JMS client > reduce number of retries

[jira] [Updated] (AMQ-7039) consumer.receive(timeout) doesn't wait for timeout when the broker has a 0 QueuePrefetch PolicyEntry and is killed

[ https://issues.apache.org/jira/browse/AMQ-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7039: -- Summary: consumer.receive(timeout) doesn't wait for timeout when the broker has a 0

[jira] [Updated] (AMQ-7042) reduce number of retries when nonBlockingRedelivery is true

[ https://issues.apache.org/jira/browse/AMQ-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7042: -- Affects Version/s: 5.13.3 > reduce number of retries when nonBlockingRedelivery is true

[jira] [Assigned] (AMQ-7042) reduce number of retries when nonBlockingRedelivery is true

[ https://issues.apache.org/jira/browse/AMQ-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-7042: - Assignee: Jean-Baptiste Onofré > reduce number of retries when

[jira] [Updated] (AMQ-7042) reduce number of retries when nonBlockingRedelivery is true

[ https://issues.apache.org/jira/browse/AMQ-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Harper updated AMQ-7042: Description: It might be useful to have a global redelivery delay that is used to reduce the number of

[jira] [Updated] (AMQ-7042) reduce number of retries when nonBlockingRedelivery is true

[ https://issues.apache.org/jira/browse/AMQ-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7042: -- Component/s: Broker > reduce number of retries when nonBlockingRedelivery is true >

[jira] [Updated] (AMQ-7040) consumer.receive(timeout) blocks infinitely if the connection is not started for vm://localhost uris with policyentry QueuePrefetch=0

[ https://issues.apache.org/jira/browse/AMQ-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7040: -- Component/s: JMS client > consumer.receive(timeout) blocks infinitely if the connection

[jira] [Updated] (AMQ-7040) consumer.receive(timeout) blocks infinitely if the connection is not started for vm://localhost uris with policyentry QueuePrefetch=0

[ https://issues.apache.org/jira/browse/AMQ-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7040: -- Affects Version/s: 5.13.3 > consumer.receive(timeout) blocks infinitely if the

[jira] [Updated] (AMQ-7040) consumer.receive(timeout) blocks infinitely if the connection is not started for vm://localhost uris with policyentry QueuePrefetch=0

[ https://issues.apache.org/jira/browse/AMQ-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7040: -- Summary: consumer.receive(timeout) blocks infinitely if the connection is not started

[jira] [Updated] (AMQ-7039) consummer.receive(timeout) doesn't wait for timeout when the broker has a 0 QueuePrefetch PolicyEntry and is killed

[ https://issues.apache.org/jira/browse/AMQ-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7039: -- Component/s: JMS client > consummer.receive(timeout) doesn't wait for timeout when the

[jira] [Assigned] (AMQ-7040) consumer.receive(timeout) blocks infinitely if the connection is not started for vm://localhost uris with policyentry QueuePrefetch=0

[ https://issues.apache.org/jira/browse/AMQ-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-7040: - Assignee: Jean-Baptiste Onofré > consumer.receive(timeout) blocks infinitely if

[jira] [Assigned] (AMQ-7039) consummer.receive(timeout) doesn't wait for timeout when the broker has a 0 QueuePrefetch PolicyEntry and is killed

[ https://issues.apache.org/jira/browse/AMQ-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-7039: - Assignee: Jean-Baptiste Onofré > consummer.receive(timeout) doesn't wait for

[jira] [Updated] (AMQ-7039) consummer.receive(timeout) doesn't wait for timeout when the broker has a 0 QueuePrefetch PolicyEntry and is killed

[ https://issues.apache.org/jira/browse/AMQ-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7039: -- Affects Version/s: 5.13.3 > consummer.receive(timeout) doesn't wait for timeout when the

[jira] [Closed] (AMQ-7119) Which is the replacement for kahaDB-5.7.0.jar in ActiveMQ 5.15.7 ??

[ https://issues.apache.org/jira/browse/AMQ-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7119. - Resolution: Fixed > Which is the replacement for kahaDB-5.7.0.jar in ActiveMQ 5.15.7 ?? >

[jira] [Updated] (AMQ-7114) The inactive queues deleted via gcInactiveDestinations reappear on activemq restart

[ https://issues.apache.org/jira/browse/AMQ-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-7114: -- Fix Version/s: WAITING_FOR_TEST > The inactive queues deleted via gcInactiveDestinations reappear on

[jira] [Commented] (AMQ-7114) The inactive queues deleted via gcInactiveDestinations reappear on activemq restart

[ https://issues.apache.org/jira/browse/AMQ-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708762#comment-16708762 ] Timothy Bish commented on AMQ-7114: --- You will need to provide a unit test to reproduce this issue or it

[jira] [Closed] (AMQ-7119) Which is the replacement for kahaDB-5.7.0.jar in ActiveMQ 5.15.7 ??

[ https://issues.apache.org/jira/browse/AMQ-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7119. - Resolution: Invalid In the future support questions should be asked on the users mailing list.  The

[jira] [Reopened] (AMQ-7119) Which is the replacement for kahaDB-5.7.0.jar in ActiveMQ 5.15.7 ??

[ https://issues.apache.org/jira/browse/AMQ-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reopened AMQ-7119: --- > Which is the replacement for kahaDB-5.7.0.jar in ActiveMQ 5.15.7 ?? >