[jira] [Commented] (ARTEMIS-3214) apply automatic page-in when all messages in a queue have expired

[ https://issues.apache.org/jira/browse/ARTEMIS-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17312236#comment-17312236 ] Gary Tully commented on ARTEMIS-3214: - this looks like a bug, set 50k maxSizeBytes, send 100k 1k

[jira] [Commented] (AMQ-8209) XATransactionId.stringFormDefault(...) creates malformed hex strings

[ https://issues.apache.org/jira/browse/AMQ-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310536#comment-17310536 ] Gary Tully commented on AMQ-8209: - good catch, that code was intentionally duplicated from aries[1] such

[jira] [Updated] (ARTEMIS-3200) ProtonAbstractReceiver memory leak

[ https://issues.apache.org/jira/browse/ARTEMIS-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated ARTEMIS-3200: Priority: Blocker (was: Major) > ProtonAbstractReceiver memory leak >

[jira] [Resolved] (ARTEMIS-3128) Queue browser may cause OutOfMemoryError on server side

[ https://issues.apache.org/jira/browse/ARTEMIS-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3128. - Assignee: Gary Tully Resolution: Fixed > Queue browser may cause OutOfMemoryError on

[jira] [Commented] (ARTEMIS-3128) Queue browser may cause OutOfMemoryError on server side

[ https://issues.apache.org/jira/browse/ARTEMIS-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309459#comment-17309459 ] Gary Tully commented on ARTEMIS-3128: - I did a little sanity check debug and an amqp large message

[jira] [Commented] (ARTEMIS-3128) Queue browser may cause OutOfMemoryError on server side

[ https://issues.apache.org/jira/browse/ARTEMIS-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309425#comment-17309425 ] Gary Tully commented on ARTEMIS-3128: - I think the linked issues help here, but there may be still

[jira] [Updated] (ARTEMIS-3128) Queue browser may cause OutOfMemoryError on server side

[ https://issues.apache.org/jira/browse/ARTEMIS-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated ARTEMIS-3128: Fix Version/s: 2.18.0 > Queue browser may cause OutOfMemoryError on server side >

[jira] [Resolved] (ARTEMIS-173) Document migration path for all activemq5 features

[ https://issues.apache.org/jira/browse/ARTEMIS-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-173. Fix Version/s: (was: unscheduled) 2.17.0 Assignee: Gary Tully

[jira] [Commented] (ARTEMIS-2630) Veracode XSS in migration-guide

[ https://issues.apache.org/jira/browse/ARTEMIS-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308736#comment-17308736 ] Gary Tully commented on ARTEMIS-2630: - short term, there may be an simple fix with some version

[jira] [Commented] (ARTEMIS-2630) Veracode XSS in migration-guide

[ https://issues.apache.org/jira/browse/ARTEMIS-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308735#comment-17308735 ] Gary Tully commented on ARTEMIS-2630: - this is interesting. Having the docs on the broker and

[jira] [Resolved] (AMQ-8202) VirtualTopic concurrentSend can break mKahaDB

[ https://issues.apache.org/jira/browse/AMQ-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-8202. - Resolution: Fixed > VirtualTopic concurrentSend can break mKahaDB >

[jira] [Created] (AMQ-8202) VirtualTopic concurrentSend can break mKahaDB

Gary Tully created AMQ-8202: --- Summary: VirtualTopic concurrentSend can break mKahaDB Key: AMQ-8202 URL: https://issues.apache.org/jira/browse/AMQ-8202 Project: ActiveMQ Issue Type: Bug Affects

[jira] [Commented] (ARTEMIS-3200) ProtonAbstractReceiver memory leak

[ https://issues.apache.org/jira/browse/ARTEMIS-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307025#comment-17307025 ] Gary Tully commented on ARTEMIS-3200: - you may want to investigate a connection pool on the spring

[jira] [Commented] (ARTEMIS-3200) ProtonAbstractReceiver memory leak

[ https://issues.apache.org/jira/browse/ARTEMIS-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307014#comment-17307014 ] Gary Tully commented on ARTEMIS-3200: - on a brief inspection, it looks like that callback does not

[jira] [Commented] (ARTEMIS-3200) ProtonAbstractReceiver memory leak

[ https://issues.apache.org/jira/browse/ARTEMIS-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307011#comment-17307011 ] Gary Tully commented on ARTEMIS-3200: -

[jira] [Updated] (ARTEMIS-3196) expose journal pool files in JMX

[ https://issues.apache.org/jira/browse/ARTEMIS-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated ARTEMIS-3196: Affects Version/s: 2.17.0 > expose journal pool files in JMX >

[jira] [Updated] (ARTEMIS-3196) expose journal pool files in JMX

[ https://issues.apache.org/jira/browse/ARTEMIS-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated ARTEMIS-3196: Fix Version/s: 2.18.0 > expose journal pool files in JMX > > >

[jira] [Resolved] (ARTEMIS-3196) expose journal pool files in JMX

[ https://issues.apache.org/jira/browse/ARTEMIS-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3196. - Resolution: Fixed > expose journal pool files in JMX > > >

[jira] [Resolved] (ARTEMIS-3194) Upgrade hawtio version to 2.13.1

[ https://issues.apache.org/jira/browse/ARTEMIS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3194. - Resolution: Fixed > Upgrade hawtio version to 2.13.1 > > >

[jira] [Updated] (ARTEMIS-3194) Upgrade hawtio version to 2.13.1

[ https://issues.apache.org/jira/browse/ARTEMIS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated ARTEMIS-3194: Fix Version/s: 2.18.0 > Upgrade hawtio version to 2.13.1 > > >

[jira] [Updated] (ARTEMIS-3194) Upgrade hawtio version to 2.13.1

[ https://issues.apache.org/jira/browse/ARTEMIS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated ARTEMIS-3194: Affects Version/s: 2.17.0 > Upgrade hawtio version to 2.13.1 >

[jira] [Resolved] (ARTEMIS-3168) JAAS login module to convert existing Principal to an Artemis UserPrincipal

[ https://issues.apache.org/jira/browse/ARTEMIS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3168. - Resolution: Fixed > JAAS login module to convert existing Principal to an Artemis

[jira] [Resolved] (ARTEMIS-3197) Add selectorAware option to the openwire virtualTopicConsumerWildcards feature

[ https://issues.apache.org/jira/browse/ARTEMIS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3197. - Resolution: Fixed > Add selectorAware option to the openwire virtualTopicConsumerWildcards

[jira] [Resolved] (ARTEMIS-3175) Restrict/truncate messages attributes to a configurable limit for management views

[ https://issues.apache.org/jira/browse/ARTEMIS-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3175. - Resolution: Fixed > Restrict/truncate messages attributes to a configurable limit for

[jira] [Created] (ARTEMIS-3197) Add selectorAware option to the openwire virtualTopicConsumerWildcards feature

Gary Tully created ARTEMIS-3197: --- Summary: Add selectorAware option to the openwire virtualTopicConsumerWildcards feature Key: ARTEMIS-3197 URL: https://issues.apache.org/jira/browse/ARTEMIS-3197

[jira] [Commented] (ARTEMIS-3190) AMQ222289: Did not route to any matching bindings on dead-letter-address DLQ and auto-create-dead-letter-resources is true

[ https://issues.apache.org/jira/browse/ARTEMIS-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306085#comment-17306085 ] Gary Tully commented on ARTEMIS-3190: - With that dlq auto creation, it looks like the broker will

[jira] [Commented] (ARTEMIS-3180) Consumers with wildcards addresses broken

[ https://issues.apache.org/jira/browse/ARTEMIS-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17304225#comment-17304225 ] Gary Tully commented on ARTEMIS-3180: - [~erwindon] fair point. I must admit to being surprised by

[jira] [Resolved] (ARTEMIS-3180) Consumers with wildcards addresses broken

[ https://issues.apache.org/jira/browse/ARTEMIS-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3180. - Fix Version/s: 2.18.0 Resolution: Fixed > Consumers with wildcards addresses broken >

[jira] [Updated] (ARTEMIS-3175) Restrict/truncate messages attributes to a configurable limit for management views

[ https://issues.apache.org/jira/browse/ARTEMIS-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated ARTEMIS-3175: Description: We still populate lots of per message data. ARTEMIS-3141 limits the number of

[jira] [Assigned] (ARTEMIS-3178) Provide a way to limit the size of an address

[ https://issues.apache.org/jira/browse/ARTEMIS-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned ARTEMIS-3178: --- Assignee: Gary Tully > Provide a way to limit the size of an address >

[jira] [Commented] (ARTEMIS-3180) Consumers with wildcards addresses broken

[ https://issues.apache.org/jira/browse/ARTEMIS-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300416#comment-17300416 ] Gary Tully commented on ARTEMIS-3180: - This looks related to ARTEMIS-3033 I will try and have a

[jira] [Assigned] (ARTEMIS-3180) Consumers with wildcards addresses broken

[ https://issues.apache.org/jira/browse/ARTEMIS-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned ARTEMIS-3180: --- Assignee: Gary Tully > Consumers with wildcards addresses broken >

[jira] [Created] (ARTEMIS-3178) Provide a way to limit the size of an address

Gary Tully created ARTEMIS-3178: --- Summary: Provide a way to limit the size of an address Key: ARTEMIS-3178 URL: https://issues.apache.org/jira/browse/ARTEMIS-3178 Project: ActiveMQ Artemis

[jira] [Updated] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages

[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated ARTEMIS-3141: Description: The list methods of queue control that are exposed via jmx seem to be unbounded.

[jira] [Created] (ARTEMIS-3175) Restrict/truncate messages attributes to a configurable limit for management views

Gary Tully created ARTEMIS-3175: --- Summary: Restrict/truncate messages attributes to a configurable limit for management views Key: ARTEMIS-3175 URL: https://issues.apache.org/jira/browse/ARTEMIS-3175

[jira] [Created] (ARTEMIS-3173) Queue control browse message in paged mode should not start from the beginning each time

Gary Tully created ARTEMIS-3173: --- Summary: Queue control browse message in paged mode should not start from the beginning each time Key: ARTEMIS-3173 URL: https://issues.apache.org/jira/browse/ARTEMIS-3173

[jira] [Resolved] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages

[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3141. - Fix Version/s: 2.18.0 Resolution: Fixed > limit the amount of data returned from

[jira] [Comment Edited] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages

[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298798#comment-17298798 ] Gary Tully edited comment on ARTEMIS-3141 at 3/10/21, 12:55 PM: I have

[jira] [Commented] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages

[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298798#comment-17298798 ] Gary Tully commented on ARTEMIS-3141: - I have settled on fixing 'management-browse-page-size' and

[jira] [Assigned] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages

[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned ARTEMIS-3141: --- Assignee: Gary Tully > limit the amount of data returned from jmx/queue control

[jira] [Comment Edited] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages

[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298699#comment-17298699 ] Gary Tully edited comment on ARTEMIS-3141 at 3/10/21, 11:24 AM: >From

[jira] [Commented] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages

[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298703#comment-17298703 ] Gary Tully commented on ARTEMIS-3141: - 'management-messages-max' may be the most intuitive and

[jira] [Commented] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages

[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298699#comment-17298699 ] Gary Tully commented on ARTEMIS-3141: - >From the doc, there is: management-browse-page-size is the

[jira] [Updated] (ARTEMIS-3168) JAAS login module to convert existing Principal to an Artemis UserPrincipal

[ https://issues.apache.org/jira/browse/ARTEMIS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated ARTEMIS-3168: Description: Artemis verifies that an authenticated subject always has an Artemis UserPrincipal

[jira] [Created] (ARTEMIS-3168) JAAS login module to convert existing Principal to an Artemis UserPrincipal

Gary Tully created ARTEMIS-3168: --- Summary: JAAS login module to convert existing Principal to an Artemis UserPrincipal Key: ARTEMIS-3168 URL: https://issues.apache.org/jira/browse/ARTEMIS-3168 Project:

[jira] [Commented] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages

[ https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17290048#comment-17290048 ] Gary Tully commented on ARTEMIS-3141: - there is a browse method, that is paged, which is more

[jira] [Comment Edited] (ARTEMIS-3135) AMQ222214: Destination q has an inconsistent and negative address size=-6

[ https://issues.apache.org/jira/browse/ARTEMIS-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17290039#comment-17290039 ] Gary Tully edited comment on ARTEMIS-3135 at 2/24/21, 3:55 PM: ---

[jira] [Commented] (ARTEMIS-3135) AMQ222214: Destination q has an inconsistent and negative address size=-6

[ https://issues.apache.org/jira/browse/ARTEMIS-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17290039#comment-17290039 ] Gary Tully commented on ARTEMIS-3135: - [~erwindon] I have reworked the fix to be more direct, which

[jira] [Created] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages

Gary Tully created ARTEMIS-3141: --- Summary: limit the amount of data returned from jmx/queue control listMessages Key: ARTEMIS-3141 URL: https://issues.apache.org/jira/browse/ARTEMIS-3141 Project:

[jira] [Resolved] (ARTEMIS-3135) AMQ222214: Destination q has an inconsistent and negative address size=-6

[ https://issues.apache.org/jira/browse/ARTEMIS-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3135. - Fix Version/s: 2.18.0 Resolution: Fixed > AMQ14: Destination q has an inconsistent

[jira] [Commented] (ARTEMIS-3135) AMQ222214: Destination q has an inconsistent and negative address size=-6

[ https://issues.apache.org/jira/browse/ARTEMIS-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288660#comment-17288660 ] Gary Tully commented on ARTEMIS-3135: - [~erwindon] thanks for your efforts to create a reproducer,

[jira] [Commented] (ARTEMIS-3135) AMQ222214: Destination q has an inconsistent and negative address size=-6

[ https://issues.apache.org/jira/browse/ARTEMIS-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288624#comment-17288624 ] Gary Tully commented on ARTEMIS-3135: - This issues is caused by ARTEMIS-3067, the memory estimate

[jira] [Assigned] (ARTEMIS-3135) AMQ222214: Destination q has an inconsistent and negative address size=-6

[ https://issues.apache.org/jira/browse/ARTEMIS-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned ARTEMIS-3135: --- Assignee: Gary Tully > AMQ14: Destination q has an inconsistent and negative address

[jira] [Comment Edited] (ARTEMIS-3125) AMQ222214: Destination X has an inconsistent and negative address size=-6

[ https://issues.apache.org/jira/browse/ARTEMIS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17287116#comment-17287116 ] Gary Tully edited comment on ARTEMIS-3125 at 2/19/21, 3:15 PM: --- I am not

[jira] [Commented] (ARTEMIS-3125) AMQ222214: Destination X has an inconsistent and negative address size=-6

[ https://issues.apache.org/jira/browse/ARTEMIS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17287116#comment-17287116 ] Gary Tully commented on ARTEMIS-3125: - I am not seeing this, I have the test scenario in one of the

[jira] [Comment Edited] (ARTEMIS-3125) AMQ222214: Destination X has an inconsistent and negative address size=-6

[ https://issues.apache.org/jira/browse/ARTEMIS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17286463#comment-17286463 ] Gary Tully edited comment on ARTEMIS-3125 at 2/18/21, 1:05 PM: --- That is

[jira] [Commented] (ARTEMIS-3125) AMQ222214: Destination X has an inconsistent and negative address size=-6

[ https://issues.apache.org/jira/browse/ARTEMIS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17286463#comment-17286463 ] Gary Tully commented on ARTEMIS-3125: - That is for sure odd, would you be able to produce a little

[jira] [Resolved] (AMQ-8142) Found SLF4J multiple bindings after adding activemq-all-5.6.0.jar file to jmeter/lib directory.

[ https://issues.apache.org/jira/browse/AMQ-8142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-8142. - Resolution: Information Provided these types of questions are better dealt with on the user list.

[jira] [Moved] (AMQ-8142) Found SLF4J multiple bindings after adding activemq-all-5.6.0.jar file to jmeter/lib directory.

[ https://issues.apache.org/jira/browse/AMQ-8142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully moved ARTEMIS-3111 to AMQ-8142: -- Key: AMQ-8142 (was: ARTEMIS-3111) Workflow: classic default workflow

[jira] [Commented] (ARTEMIS-2886) Optimize security auth

[ https://issues.apache.org/jira/browse/ARTEMIS-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279637#comment-17279637 ] Gary Tully commented on ARTEMIS-2886: - Where is the loop here, does a client in a loop doing send

[jira] [Deleted] (AMQ-8137) Most Popular And Crucial Micro-Switches - Unionwell Micro-Switches

[ https://issues.apache.org/jira/browse/AMQ-8137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully deleted AMQ-8137: > Most Popular And Crucial Micro-Switches - Unionwell Micro-Switches >

[jira] [Resolved] (ARTEMIS-3067) AMQP applicationProperties are not part of the memoryEstimate

[ https://issues.apache.org/jira/browse/ARTEMIS-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3067. - Resolution: Fixed AMQP application properties are still left encoded, however if they do get

[jira] [Updated] (AMQ-8131) JDBC Store - durable topic with non matching selector can hold message till unsubscribe requires enableMessageExpirationOnActiveDurableSubs

[ https://issues.apache.org/jira/browse/AMQ-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-8131: Description: Unmatched messages get an unmatched ack, however this ack is ignored by the topic message

[jira] [Updated] (AMQ-8131) JDBC Store - durable topic with non matching selector can hold message till unsubscribe requires enableMessageExpirationOnActiveDurableSubs

[ https://issues.apache.org/jira/browse/AMQ-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-8131: Description: Unmatched messages get an unmatched ack, however this ack is ignored by the topic message

[jira] [Resolved] (AMQ-8131) JDBC Store - durable topic with non matching selector can hold message till unsubscribe requires enableMessageExpirationOnActiveDurableSubs

[ https://issues.apache.org/jira/browse/AMQ-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-8131. - Resolution: Fixed > JDBC Store - durable topic with non matching selector can hold message till >

[jira] [Updated] (AMQ-8131) JDBC Store - durable topic with non matching selector can hold message till unsubscribe requires enableMessageExpirationOnActiveDurableSubs

[ https://issues.apache.org/jira/browse/AMQ-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-8131: Summary: JDBC Store - durable topic with non matching selector can hold message till unsubscribe requires

[jira] [Reopened] (AMQ-8131) JDBC Store - durable topic with non matching selector can hold message till unsubscribe in error

[ https://issues.apache.org/jira/browse/AMQ-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reopened AMQ-8131: - need to rethink, I see a failure in

[jira] [Commented] (AMQ-7298) failover duplicate detection in error with batched local transactions

[ https://issues.apache.org/jira/browse/AMQ-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17274437#comment-17274437 ] Gary Tully commented on AMQ-7298: - [~lichtin] would you have a test case handy? does your scenarion fail on

[jira] [Resolved] (AMQ-8131) JDBC Store - durable topic with non matching selector can hold message till unsubscribe in error

[ https://issues.apache.org/jira/browse/AMQ-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-8131. - Resolution: Fixed > JDBC Store - durable topic with non matching selector can hold message till >

[jira] [Deleted] (ARTEMIS-3088) How may Cash.app/help to make moment exchanges?

[ https://issues.apache.org/jira/browse/ARTEMIS-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully deleted ARTEMIS-3088: > How may Cash.app/help to make moment exchanges? >

[jira] [Created] (AMQ-8131) JDBC Store - durable topic with non matching selector can hold message till unsubscribe in error

Gary Tully created AMQ-8131: --- Summary: JDBC Store - durable topic with non matching selector can hold message till unsubscribe in error Key: AMQ-8131 URL: https://issues.apache.org/jira/browse/AMQ-8131

[jira] [Updated] (ARTEMIS-3064) Disable useTopologyForLoadBalancing for non HA federation connections between clusters

[ https://issues.apache.org/jira/browse/ARTEMIS-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated ARTEMIS-3064: Summary: Disable useTopologyForLoadBalancing for non HA federation connections between clusters

[jira] [Commented] (ARTEMIS-3064) Enable/Disable useTopologyForLoadBalancing for federation connections between clusters

[ https://issues.apache.org/jira/browse/ARTEMIS-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17272876#comment-17272876 ] Gary Tully commented on ARTEMIS-3064: - proving an alternative url configuration may make sense, but

[jira] [Commented] (ARTEMIS-3083) Set a default producer-window-size on cluster connection

[ https://issues.apache.org/jira/browse/ARTEMIS-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17272290#comment-17272290 ] Gary Tully commented on ARTEMIS-3083: - I think the bias here is on the cluster connection producing

[jira] [Commented] (ARTEMIS-3064) Enable/Disable useTopologyForLoadBalancing for federation connections between clusters

[ https://issues.apache.org/jira/browse/ARTEMIS-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17270093#comment-17270093 ] Gary Tully commented on ARTEMIS-3064: - i have researched this a bit, seems the norm is to put this

[jira] [Created] (ARTEMIS-3067) AMQP applicationProperties are not part of the memoryEstimate

Gary Tully created ARTEMIS-3067: --- Summary: AMQP applicationProperties are not part of the memoryEstimate Key: ARTEMIS-3067 URL: https://issues.apache.org/jira/browse/ARTEMIS-3067 Project: ActiveMQ

[jira] [Commented] (ARTEMIS-3062) Incorrect Jolokia access config when using 0.0.0.0 http-host

[ https://issues.apache.org/jira/browse/ARTEMIS-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264308#comment-17264308 ] Gary Tully commented on ARTEMIS-3062: - to have the command do it, would require a second parameter,

[jira] [Commented] (ARTEMIS-3062) Incorrect Jolokia access config when using 0.0.0.0 http-host

[ https://issues.apache.org/jira/browse/ARTEMIS-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264265#comment-17264265 ] Gary Tully commented on ARTEMIS-3062: - that http-host parameter ends up in a jolokia security

[jira] [Commented] (ARTEMIS-3064) Enable/Disable useTopologyForLoadBalancing for federation connections between clusters

[ https://issues.apache.org/jira/browse/ARTEMIS-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17263433#comment-17263433 ] Gary Tully commented on ARTEMIS-3064: - to be clear, I am thinking:

[jira] [Comment Edited] (ARTEMIS-3064) Enable/Disable useTopologyForLoadBalancing for federation connections between clusters

[ https://issues.apache.org/jira/browse/ARTEMIS-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17263432#comment-17263432 ] Gary Tully edited comment on ARTEMIS-3064 at 1/12/21, 3:36 PM: ---

[jira] [Commented] (ARTEMIS-3064) Enable/Disable useTopologyForLoadBalancing for federation connections between clusters

[ https://issues.apache.org/jira/browse/ARTEMIS-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17263432#comment-17263432 ] Gary Tully commented on ARTEMIS-3064: - [~michaelpearce] I think with ha=false is the place to put

[jira] [Created] (ARTEMIS-3064) Enable/Disable useTopologyForLoadBalancing for federation connections between clusters

Gary Tully created ARTEMIS-3064: --- Summary: Enable/Disable useTopologyForLoadBalancing for federation connections between clusters Key: ARTEMIS-3064 URL: https://issues.apache.org/jira/browse/ARTEMIS-3064

[jira] [Resolved] (ARTEMIS-3033) use a structured tree with visitors for wildcard addresses to avoid duplicate cross linking in address impl

[ https://issues.apache.org/jira/browse/ARTEMIS-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3033. - Resolution: Fixed > use a structured tree with visitors for wildcard addresses to avoid

[jira] [Closed] (AMQ-5552) introduce a smoke-test profile that is enabled by default and during release:prepare

[ https://issues.apache.org/jira/browse/AMQ-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully closed AMQ-5552. --- Resolution: Done > introduce a smoke-test profile that is enabled by default and during > release:prepare >

[jira] [Comment Edited] (ARTEMIS-3038) Investigate CoreClientOverOneWaySSLKerb5Test#testOneWaySSLWithGoodClientCipherSuite

[ https://issues.apache.org/jira/browse/ARTEMIS-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258936#comment-17258936 ] Gary Tully edited comment on ARTEMIS-3038 at 1/7/21, 12:19 PM: --- The first

[jira] [Commented] (ARTEMIS-3038) Investigate CoreClientOverOneWaySSLKerb5Test#testOneWaySSLWithGoodClientCipherSuite

[ https://issues.apache.org/jira/browse/ARTEMIS-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258936#comment-17258936 ] Gary Tully commented on ARTEMIS-3038: - The first problem (and it may be sufficient) is that the 

[jira] [Created] (ARTEMIS-3033) use a structured tree with visitors for wildcard addresses to avoid duplicate cross linking in address impl

Gary Tully created ARTEMIS-3033: --- Summary: use a structured tree with visitors for wildcard addresses to avoid duplicate cross linking in address impl Key: ARTEMIS-3033 URL:

[jira] [Commented] (ARTEMIS-3030) Journal lock evaluation fails when NFS is temporarily disconnected

[ https://issues.apache.org/jira/browse/ARTEMIS-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17249904#comment-17249904 ] Gary Tully commented on ARTEMIS-3030: - note, a combination of exists and lastModified is in place

[jira] [Resolved] (ARTEMIS-3009) Reference cluster connection message loadbalancing type from the remote binding

[ https://issues.apache.org/jira/browse/ARTEMIS-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-3009. - Resolution: Fixed > Reference cluster connection message loadbalancing type from the remote >

[jira] [Resolved] (ARTEMIS-2990) optimise performance of wildcard address manager

[ https://issues.apache.org/jira/browse/ARTEMIS-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-2990. - Fix Version/s: 2.17.0 Resolution: Fixed > optimise performance of wildcard address

[jira] [Closed] (ARTEMIS-2894) Message redistribution don't work anymore when paging start on cluster address

[ https://issues.apache.org/jira/browse/ARTEMIS-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully closed ARTEMIS-2894. --- Assignee: Gary Tully > Message redistribution don't work anymore when paging start on cluster

[jira] [Commented] (ARTEMIS-2894) Message redistribution don't work anymore when paging start on cluster address

[ https://issues.apache.org/jira/browse/ARTEMIS-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238846#comment-17238846 ] Gary Tully commented on ARTEMIS-2894: - [~Gaetan C.] great. thanks for confirming :) > Message

[jira] [Created] (ARTEMIS-3009) Reference cluster connection message loadbalancing type from the remote binding

Gary Tully created ARTEMIS-3009: --- Summary: Reference cluster connection message loadbalancing type from the remote binding Key: ARTEMIS-3009 URL: https://issues.apache.org/jira/browse/ARTEMIS-3009

[jira] [Created] (ARTEMIS-2990) optimise performance of wildcard address manager

Gary Tully created ARTEMIS-2990: --- Summary: optimise performance of wildcard address manager Key: ARTEMIS-2990 URL: https://issues.apache.org/jira/browse/ARTEMIS-2990 Project: ActiveMQ Artemis

[jira] [Resolved] (ARTEMIS-2985) MQTT should not block netty thread

[ https://issues.apache.org/jira/browse/ARTEMIS-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved ARTEMIS-2985. - Resolution: Fixed > MQTT should not block netty thread > -- >

[jira] [Created] (ARTEMIS-2985) MQTT should not block netty thread

Gary Tully created ARTEMIS-2985: --- Summary: MQTT should not block netty thread Key: ARTEMIS-2985 URL: https://issues.apache.org/jira/browse/ARTEMIS-2985 Project: ActiveMQ Artemis Issue Type:

[jira] [Commented] (AMQ-6951) Hide embedded jetty version

[ https://issues.apache.org/jira/browse/AMQ-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17229204#comment-17229204 ] Gary Tully commented on AMQ-6951: - that was sorted in Artemis in the past via: 

[jira] [Commented] (ARTEMIS-2894) Message redistribution don't work anymore when paging start on cluster address

[ https://issues.apache.org/jira/browse/ARTEMIS-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226088#comment-17226088 ] Gary Tully commented on ARTEMIS-2894: - great. we can leave this open till you confirm the release.

[jira] [Comment Edited] (ARTEMIS-2894) Message redistribution don't work anymore when paging start on cluster address

[ https://issues.apache.org/jira/browse/ARTEMIS-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17225316#comment-17225316 ] Gary Tully edited comment on ARTEMIS-2894 at 11/3/20, 11:41 AM:

[jira] [Commented] (ARTEMIS-2894) Message redistribution don't work anymore when paging start on cluster address

[ https://issues.apache.org/jira/browse/ARTEMIS-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17225316#comment-17225316 ] Gary Tully commented on ARTEMIS-2894: - [~Gaetan C.] that test passes for me on the current trunk,

<    1   2   3   4   5   6   7   8   9   10   >