[
https://issues.apache.org/jira/browse/ARTEMIS-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy A. Bish closed ARTEMIS-3639.
------------------------------------
Resolution: Won't Fix
These seems an unnecessary overhead to add to the broker which would require
more tracking and state management for little benefit
> Introduce ActiveMQServerMessagePlugin::beforeInitialSend
> --------------------------------------------------------
>
> Key: ARTEMIS-3639
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3639
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.20.0
> Reporter: Petr Kuzel
> Priority: Minor
>
> Currently ActiveMQServerMessagePlugin::beforeSend could be used to peek
> initial messages from clients.
> Heuristic can cope with detecting if the before send notification by the
> broker represents an initial message from a client or the notification
> represents a later forward inside the broker cluster (or network) like a
> redistribution or a retry after recycling message from DLQ.
> The broker should have enough context and it should know explicitly when
> dealing with an initial client message so the {{ActiveMQServerMessagePlugin}}
> interface could be improved with:
> {code:java}
> /**
> * Invoked by the broker before an initial client message is sent (inserted)
> to the broker.
> * In contrast with {@link #beforeSend} it is not called for subsequent
> message forwards
> * inside the broker cluster (like redistribution, DLQ recycling, ...).
> * <p>
> * By default it delegates to {@link #beforeSend}.
> */
> default void beforeInitialSend(ServerSession session, Transaction tx, Message
> message, boolean direct, boolean noAutoCreateQueue) throws ActiveMQException {
> beforeSend(session, tx, message, direct, noAutoCreateQueue);
> }{code}
--
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
