[
https://issues.apache.org/jira/browse/ARTEMIS-5106?focusedWorklogId=938927&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-938927
]
ASF GitHub Bot logged work on ARTEMIS-5106:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Oct/24 15:04
Start Date: 18/Oct/24 15:04
Worklog Time Spent: 10m
Work Description: tabish121 opened a new pull request, #5306:
URL: https://github.com/apache/activemq-artemis/pull/5306
If an exception is thrown in the AMQP send path and there is an active
transaction we should mark that as rollback only so the client will see an
error when it tries to commit a transaction that had a failed send.
Issue Time Tracking
-------------------
Worklog Id: (was: 938927)
Remaining Estimate: 0h
Time Spent: 10m
> Exception thrown from plugin in beforeSend method is not propagated to
> clients using AMQP protocol and creates large message orphan files
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-5106
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5106
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, Broker
> Affects Versions: 2.36.0
> Reporter: Jean-Pascal Briquet
> Priority: Minor
> Attachments: BeforeSendPluginTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *Context:*
> The following behaviour has been seen while developing a plugin intended to
> limit the size of messages accepted by Artemis.
> When a message size exceeds the configured size limit, the plugin throws an
> exception in the beforeSend method to stop further message processing within
> Artemis.
> *Details:*
> The plugin has been tested and works correctly on the following scenarios:
> - CORE protocol, standard & large messages (transacted session +
> auto-acknowledgement)
> - OPENWIRE protocol, standard & large messages (transacted session +
> auto-acknowledgement)
> - AMQP protocol, standard & large messages (auto-acknowledgement)
> However, two issues were identified when using the AMQP protocol :
> - the client does not receive any exception from Artemis when the session is
> transacted
> - if the received message is a large message, it is created on the
> filesystem but becomes an orphan, with no link to an existing message in the
> Artemis journal.
> This occurs in both transacted and auto-acknowledge session cases.
> *Client-side:*
> The JMS AMQP client tested was QPid JMS 1.12.1.
> From the QPid side, it seems that the transacted session is successfully
> commited, and no error is received.
> Therefore, it seems the error is not properly propagated to the client by
> Artemis.
> *Test case:*
> A test case is provided in attachment, including both CORE and AMQP protocol
> scenarios.
> Before running it, add the test file into the artemis folder :
> -
> tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/plugin
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
