Unknown macro: {search-box}
Child pages
  • JMS Message Types and Header Fields

This documentation is for WSO2 Message Broker version 2.1.1. View documentation for the latest release.

                                                                                                                                                                                                                                                                                                                                     
||
Skip to end of metadata
Go to start of metadata

JMS Message Types supported by WSO2 MB

WSO2 MB 2.10 supports all the five types of JMS messages named TextMessage, BytesMessage, MapMessage, ObjectMessage and StreamMessage. A JMS client can send or receive any type of message from the above five and the content of the messages can be viewed using the WSO2 MB Queue Browser window. However viewing message body of an ' ObjectMessage ' using queue browser is not supported.

JMS Message Headers supported by WSO2 MB

A JMS client can create a message and set various fields of the message header before it is sent to a queue in WSO2 MB. However as supported by the JMS specification there are several message header fields which can not be explicitly set by a JMS client. Hence even though client sets these fields, those will be replaced at the JMS provider level once it is received by WSO2 MB.

The following table displays a list of JMS message headers and in which level they can be configured.

JMS Message HeaderCan be Set by Whom
JMSDestinationJMS providers can set this field when a message is sent. Hence this field can not be set at client level and will be handled at broker level in MB
JMSDeliveryModeAs WSO2 MB uses persistent storage in Standalone Mode, the DeliveryMode will be set to '2' by default. When running MB in In-memory Mode this will be set into value '1' which reflects Non-persistent storage. Not possible to change this at client level in both scenarios.
JMSExpirationJMS providers can set this field when a message is sent. Hence this field can not be set at client level and will be handled at broker level in MB
JMSPriorityWSO2 MB doesn't support message priorities. Hence this field can not be set at client level and will be handled at broker level in MB.
JMSMessageIDJMS providers can set this field when a message is sent. Hence this field can not be set at client level and will be handled at broker level in MB
JMSTimestampJMS providers can set this field when a message is sent. Hence this field can not be set at client level and will be handled at broker level in MB
JMSCorrelationIDBy using a JMS Client
JMSReplyToBy using a JMS Client
JMSTypeBy using a JMS Client
JMSRedeliveredFrom the JMS provider only
  • No labels