Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.
This documentation is for WSO2 Message Broker version 3.2.0. For the latest documentation, see the documentation for WSO2 Enterprise Integrator.
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Custom JMS property which embeds routing key to the message.

When a message is being sent to the DLC by some means, the user/admin can select messages and redirect them to a different client. In this case, at time the client requires to know the original destination to which the message was publish to.

So from andes-client side, we are embedding the routing key to a JMS property of the message. The embedding is enabled only when “AndesSetRoutingKey” system property is set to a non-null value(any value other than null) from the publisher client side. When the mentioned system property is set, each message will have a JMS property of type string with name “JMS_ANDES_ROUTING_KEY” which will contain the routing key.

Enabling the JMS property(at publisher client) :

System.setProperty("AndesSetRoutingKey", "1");

Getting the property through a JMS message :

System.out.println("PROP:" + message.getStringProperty("JMS_ANDES_ROUTING_KEY"));

  • No labels