...
| Code Block | ||
|---|---|---|
| ||
<inboundEndpoint xmlns="http://ws.apache.org/ns/synapse" name="jms" sequence="request" onError="fault" protocol="jms" suspend="false">
<parameters>
<parameter name="interval">1000</parameter>
<parameter name="coordination">true</parameter>
<parameter name="transport.jms.Destination">ordersQueue</parameter>
<parameter name="transport.jms.CacheLevel">1<>3</parameter>
<parameter name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter>
<parameter name="sequential">true</parameter>
<parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
<parameter name="java.naming.provider.url">tcp://localhost:61616</parameter>
<parameter name="transport.jms.SessionAcknowledgement">AUTO_ACKNOWLEDGE</parameter>
<parameter name="transport.jms.SessionTransacted">false</parameter>
<parameter name="transport.jms.ConnectionFactoryType">queue</parameter>
</parameters>
</inboundEndpoint> |
...
Parameter Name | Description | Required | Possible Values | Default Value | |||||
|---|---|---|---|---|---|---|---|---|---|
| The JNDI initial context factory class. The class must implement the | Yes | A valid class name | - | |||||
| The URL of the JNDI provider. | Yes | A valid URL | - | |||||
| The JNDI name of the connection factory. | Yes | - | - | |||||
| Whether the messages need to be polled and injected sequentially or not. | Yes | true, false | true | |||||
| The type of the connection factory. | No |
|
| |||||
| The JNDI name of the destination. | No | - | The defaults value is the service name. | |||||
| Whether the JMS session should be transacted or not. | No |
|
| |||||
| The JMS session acknowledgment mode. | No |
|
| |||||
| The JMS resource cache level. | No | 0 -
|
| |||||
| The JMS connection username. | No | - | - | |||||
| The JMS connection password. | No | - | - | |||||
| The JMS API version. | No |
|
| |||||
transport.jms.SubscriptionDurable | Whether the connection factory is subscription durable or not. | No | true, false | false | |||||
transport.jms.DurableSubscriberClientID | The ClientId parameter when using durable subscriptions. | Required if the value specified as transport.jms.SubscriptionDurable is true. | - | - | |||||
| The name of the durable subscriber. | Required if the value specified as | - | - | |||||
| Message selector implementation. | No | |||||||
| The time to wait for a JMS message during polling. Set this parameter value to a negative integer to wait indefinitely. Set it to zero to prevent waiting. | No | The number of milliseconds to wait. | 1 | |||||
transport.jms.ContentType | How the inbound listener should determine the content type of received messages. Priority is always given to the JMS message type. | No | A simple string value, in which case the transport listener assumes that the received messages always have the specified content type, or a set of rules. For more information, see http://axis.apache.org/axis2/java/transports/jms.html#Service_configuration. | - | |||||
transport.jms.ContentTypeProperty | Get the content type from message property | No | contentType | - | |||||
transport.jms.ReplyDestination | The destination that the response generated by the back-end service is stored. | No | - | ReplyTo from the message | |||||
| Whether messages should be published via the same connection that they were received. | No | true, false | false | |||||
| The retry interval to reconnect to the JMS server. | No | Retry interval in miliseconds. | ||||||
| The number of consecutive mediation failures after which polling should be suspended. | No | Specify any positive numerical value based on your requirement. Polling will be suspended when the mediation failure count reaches the specified value. | - | |||||
| The period of time that polling is to be suspended when the transport.jms.PollingSuspensionLimitRetriesBeforeSuspension parameter is set. | No | Specify a required time period in milliseconds. | 60000 |
...
| title | Note |
|---|
...
Samples
For a sample that demonstrates how one way message bridging from JMS to HTTP can be done using the JMS inbound endpoint, see Sample 901: Inbound Endpoint JMS Protocol Sample.