Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-5134

Consumption Stalled after seeing AMQ222151 and org.apache.activemq.artemis.core.paging.cursor.NonExistentPage ERRORS in log

    XMLWordPrintable

Details

    Description

      After seeing warnings related to ENTMQBR-2100 and ENTMQBR-2201 in the broker log, consumption on affected addresses stops and does not recover until a broker restart.

      Symptoms of the issue include log errors / warnings like:

      artemisf4.log.9:2021-06-18 11:14:41,479 WARN  [org.apache.activemq.artemis.core.server] AMQ222242: Unable to obtain message priority, using default : org.apache.activemq.artemis.core.paging.cursor.NonExistentPage: Invalid messageNumber passed = PagePositionImpl [pageNr=8926, messageNr=697, recordID=938678408, fileOffset=5967014] on null

      2021-06-18 11:55:37,063 WARN  [org.apache.activemq.artemis.core.server] AMQ222151: removing consumer which did not handle a message, consumer=ServerConsumerImpl [id=0, filter=null, binding=LocalQueueBinding [address=######, queue=QueueImpl[name=#######, postOffice=PostOfficeImpl [server=ActiveMQServerImpl::serverUUID=c7a2571d-cde2-11eb-9190-9440c9805db0], temp=false]@432dbe28, filter=null, name=#######, clusterName=#######c7a2571d-cde2-11eb-9190-9440c9805db0]], message=PagedReferenceImpl [position=PagePositionImpl [pageNr=8639, messageNr=360, recordID=923389898, fileOffset=4256027], message=error:Invalid messageNumber passed = PagePositionImpl [pageNr=8639, messageNr=360, recordID=923389898, fileOffset=4256027] on null, deliveryTime=0, persistedCount=0, deliveryCount=1, subscription=PageSubscriptionImpl [cursorId=1272113, queue=QueueImpl[name=#######, postOffice=PostOfficeImpl [server=ActiveMQServerImpl::serverUUID=c7a2571d-cde2-11eb-9190-9440c9805db0], temp=false]@432dbe28, filter = null]]: org.apache.activemq.artemis.core.paging.cursor.NonExistentPage: Invalid messageNumber passed = PagePositionImpl [pageNr=8639, messageNr=360, recordID=923389898, fileOffset=4256027] on null

      and 

      2021-06-17 03:38:27,177 WARN  [org.apache.activemq.artemis.core.server] AMQ222144: Queue could not finish waiting executors. Try increasing the thread pool size.

      It is unclear from the timing of the warnings whether the thread pool pressure was a consequence of or contributor to the issue, as the issue is already in progress from the head of the available logs.

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-4822 [LTS] Inconsistencies between Replication Catchup and PagingStore.stopPaging();

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2100 AMQ 7.2.1: under heavy load: org.apache.activemq.artemis.core.paging.cursor.NonExistentPage: Invalid messageNumber passed

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2201 Repeated sending, receiving and disconnecting will freeze .NET Client

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-4801 OpenWire protocol should use ConcurrentHashMap instead of HashMap to avoid potential performance degradation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              csuconic@redhat.com Clebert Suconic
              rhn-support-dhawkins Duane Hawkins
              Roman Vais Roman Vais
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: