You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2022/09/27 14:31:00 UTC

[jira] [Commented] (ARTEMIS-4018) Upgrade: existing paged messages not delivered to consumers

    [ https://issues.apache.org/jira/browse/ARTEMIS-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610092#comment-17610092 ] 

Justin Bertram commented on ARTEMIS-4018:
-----------------------------------------

I split this up into 2 separate Jiras. See ARTEMIS-4019.

> Upgrade: existing paged messages not delivered to consumers
> -----------------------------------------------------------
>
>                 Key: ARTEMIS-4018
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4018
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>         Environment: SUSE Linux Enterprise Server 15 SP3
> JAVA_ARGS="-XX:+PrintClassHistogram -XX:+UseG1GC -XX:+UseStringDeduplication -Xms512M -Xmx4G -Dhawtio.disableProxy=true -Dhawtio.realm=activemq -Dhawtio.offline=true -Dhawtio.rolePrincipalClasses=org.apache.activemq.artemis.spi.core.security.jaas.RolePrincipal -Djolokia.policyLocation=${ARTEMIS_INSTANCE_ETC_URI}jolokia-access.xml "
>            Reporter: Peter Machon
>            Priority: Major
>
> After upgrading from version 2.22.0 to 2.25.0 we were facing a situation where messages, already queued or paged before the upgrade are not delivered to consumers. New messages, arriving at the broker after the upgrade were handled normally.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)