[
https://issues.apache.org/jira/browse/ARTEMIS-4095?focusedWorklogId=868496&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-868496
]
ASF GitHub Bot logged work on ARTEMIS-4095:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 29/Jun/23 16:31
Start Date: 29/Jun/23 16:31
Worklog Time Spent: 10m
Work Description: artyom-tarasenko commented on PR #4529:
URL:
https://github.com/apache/activemq-artemis/pull/4529#issuecomment-1613500182
> I'm still confused because the `internalSession` from
`org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection` is a
`org.apache.activemq.artemis.core.server.ServerSession` whereas the `session`
variable being checked in
`org.apache.activemq.artemis.core.protocol.openwire.amq.AMQConsumer#handleDeliver`
(which you changed) is a
`org.apache.activemq.artemis.core.protocol.openwire.amq.AMQSession`. I don't
see the overlap here. This value appears to be coming from the OpenWire
_client_.
The bug is triggered when the message is delivered to a client. The way from
the client to server accounts clientid, but when the message is consumed by ra
client the CONNECTION_ID_PROPERTY is removed. If I understand the flow
correctly, the server opens a transaction, creates an internal session and uses
it to transfer the data to a subscriber.
Issue Time Tracking
-------------------
Worklog Id: (was: 868496)
Time Spent: 1h (was: 50m)
> OpenWire clients are unable to consume from mutlicast queue after 2nd paging
> ----------------------------------------------------------------------------
>
> Key: ARTEMIS-4095
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4095
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 2.26.0, 2.27.0, 2.27.1, 2.28.0, 2.29.0
> Environment: Artemis, deployed through the official docker image in
> version {{2.26.0}} in an OpenShift cluster
> Reporter: Marco Bungart
> Priority: Major
> Attachments:
> 0001-ARTEMIS-4095-fix-delivering-message-size-accounting.patch,
> artemis-Xmx1G.png, artemis-Xmx2G.png, graph1.png, graph2.png,
> jmeter-orders-6500-localhost.jmx, jmsconsumer-1.0-SNAPSHOT.jar
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> I observed that after artemis went into paging for the 2nd time, OpenWire
> clients were not able to read messages from their corresponding addresses.
> Restarting the applications connected as clients does not fix the issue.
> Restarting artemis, however, does fix the issue.
> Both images attached show the messages of two queues.
> - The upper (orange) line in the 1st graph shows count of messages in a queue
> to which core clients are connected.
> - The lower (blue) line in the 1stg raph shows count of messages in a queue
> to which OpenWire clients are connected.
> - in the 2nd graph, the upper (violet) line shows count of messages in a
> queue to which core clients are connected.
> - in the 2nd graph, the lower (green) line shows count of messages in a queue
> to which OpenWire clients are connected.
> I have a heap dump that we could share, showing the accumulated objects. the
> dump is about 90 MB in size If this would be helpful to have, please let me
> know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
