The WSO2 ESB JMS inbound protocol is a multi-tenant capable alternative to the WSO2 ESB JMS transport. The JMS inbound protocol implementation requires an active JMS server instance to be able to receive messages, and you need to place the client JARs for your JMS server in the ESB classpath.

The recommended JMS servers are WSO2 Message Broker or Apache ActiveMQ, but other implementations such as Apache Qpid and Tibco are also supported.

The destination that the response generated by the back-end service is stored.

No

-

ReplyTo from the message

transport.jms.PubSubNoLocal

Whether messages should be published via the same connection that they were received.

No

true, false

false

transport.jms.SharedSubscription

If set to true, messages will be forwarded to only one of the consumers and consumers will share the messages that are published to the topic.

No

true, false

false

pinnedServers

List of synapse server names separated by commas or spaces where this inbound endpoint should be deployed. If there is no pinned server list, the inbound endpoint configuration will be deployed in all server instances.

No

List of valid synapse server names

-

transport.jms.ConcurrentConsumers

Number of concurrent threads to be started to consume messages when polling.

No

Any positive integer.For topics this must always be 1.

1

transport.jms.retry.duration

The retry interval to reconnect to the JMS server.

No

Retry interval in miliseconds.

-

Samples

See the samples on how one-way message bridging from JMS to HTTP can be done using the JMS inbound endpoint: