Couple of thoughts here: - Necessary properties and/or payload should really be set by the producers themselves. This should be part of the messaging "contract" (e.g. like an API) used to govern communication between application components. - One of the main strengths of asynchronous messaging is the decoupling of producers and consumers as this allows applications to scale much more easily. Take care not to inadvertently recouple these. - Depending on the protocol you're using it may not be possible to modify the message's payload. For example, I believe the AMQP message payload is immutable by spec.
Justin On Thu, May 29, 2025 at 4:05 PM William Crowell <wcrow...@perforce.com.invalid> wrote: > In Apache Artemis Is it possible to send the external IP of clients > publishing messages in a message header and/or property or add something to > the broker configuration to put it in the message payload? I know that > connection routers have access to the SOURCE_IP. > > Regards, > > William Crowell > > > This e-mail may contain information that is privileged or confidential. If > you are not the intended recipient, please delete the e-mail and any > attachments and notify us immediately. > >
