The JMS provider type that is to be used for the JMS Messaging Service.

You can select one of the following JMS providers:

When you select a JMS provider type, a list of initial context properties that contain pre-defined default settings for the selected JMS provider appears. You can update the values that appear in the

Initial Context Properties

section.

You can specify any provider that provides JNDI access to JMS resources. If the provider that you want to use is not available in the list, you can select

Other JMS

to populate the configuration with commonly used, generic JNDI properties.

If you select the

IBM WebSphere

provider type, you will not be able to configure the queue listener and topic listener properties and the following message appears:

Configuration of Queue and Topic listeners is not available with the Websphere JMS provider. Websphere JMS explicitly forbids creating asynchronous consumers outside of a message-driven bean deployment when running on a Websphere server.

The JNDI name of the JMS connection factory.

Indicates whether to include user credentials while creating connections on the connection factory.

If the provider is hosted by an application server, you do not need to configure the connection user because authentication takes place when you access objects through the JNDI context.

IBM MQ Series is a provider that requires connection credentials.

Each JMS Manager maintains an internal pool of connections to enhance performance when interacting with a remote JMS provider.

This option sets the maximum number of active connections allowed at any time. This includes connections used for asynchronous listeners configured under

Queues and Listeners

,

Topics and Listeners

, and those used for invoke activities. If the maximum number is reached, clients must wait until a connection is returned to the pool.

Setting the maximum value to -1 indicates that the manager may create as many connections as needed, with no upper limit so clients never have to wait. Change this value from the default of -1 if more connections are being created than the JMS provider can handle.

Configure one of the following values:

-1 (unlimited)
A number higher than the total number of listeners for queues, topics, and some connections for invoke activities

Default is

-1

.

Sets the number of unused connections the manager retains at any one time. If a connection is returned to the pool, and there are already the maximum free connections sitting idle, the connection is closed. This allows the total number of connections from the pool to shrink and grow as necessary. Setting the maximum free connections to 0 prevents the Process Server from holding onto connections. Each client receives a newly created connection.

Ensure that the value of the

Maximum Free Connections

field is lower than the value of the

Maximum Total Connections

field.

Default is

15

.

This option controls whether or not the JMS provider persists messages to storage for all processes. An individual process can have a different persistence setting, which overrides this option.

Enable this option to persist messages in the event of a JMS failure. When this mode is enabled, Process Server instructs the JMS provider to ensure that a message is not lost in transit in case of a JMS provider failure. It is logged to stable storage.

Note that persistent delivery requires that your JMS provider be configured with storage. Also, there is usually a performance hit with persisting messages.

Default is

Persistent

.

Specifies the amount of time an unconsumed message remains on a queue. If a message will become obsolete after a certain period, you might want to set an expiration time. The expiration of obsolete messages conserves storage and computing resources.

Default is

0 milliseconds

, which means that the default for the provider is used. This means that messages never expire and remain on the queue forever.

Specifies a non-negative integer for a message handling priority. Default is

0

, which means that the default for the provider is used. An individual process can specify a priority, which overrides this option.

JMS defines a 10-level priority value with 0 as the lowest and 9 as the highest. Clients must consider 0-4 as gradients of normal priority and 5-9 as gradients of expedited priority. Priority is set to 4, by default.

Specifies the maximum number of reconnection attempts that the JMS Manager must make when it tries to connect to the JMS provider.

Enter

-1

for unlimited reconnection attempts.

Default is

20

.

When you stop the JMS Manager, the reconnection attempt is also stopped.

Specifies the number of milliseconds to wait between each connection retry attempt.

For example, to retry to connect up to 10 times with a 10000 millisecond delay between retries, set the

Maximum Reconnect Attempts

field to

10

and the

Reconnect Interval (ms)

field to

10000

.

Default is

30000 milliseconds

.