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

[jira] [Commented] (ARTEMIS-4018) Existing paged messages not delivered to consumers after upgrade

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

Peter Machon commented on ARTEMIS-4018:
---------------------------------------

I am not sure, if this issue is hidden somewhere else.

We moved the old journal away and restarted our broker with an empty journal. Most things seems fine. However, there is one queue that (after several restarts of broker and client) apparently shows similar behaviour as above.
The management interface shows a fixed amount of messages that remains in the respective (anycast) queue and doesn't get acknowledged by the consumer. New messages are handled as expected. However, browsing the queue that claims to contain more than 3000 messages returns an empty list. 
Not sure if that is even related to the original issue, but may be a hint.

> Existing paged messages not delivered to consumers after upgrade
> ----------------------------------------------------------------
>
>                 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)