WebSphere Application Server Network Deployment, Version 6.1
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

Message listener service custom properties

Use this panel to view or change an optional set of name and value pairs for custom properties of the message listener service.

To view this administrative console page, click Servers > Application Servers > server_name > [Communications] Messaging > Message Listener Service > Custom Properties

You can use the Custom properties page to define the following properties for use by the message listener service.
DYNAMIC.CONFIGURATION.ENABLED

This property controls whether the application server on which a listener port is created requires to be restarted. Set this property to true to enable dynamic configuration. This property is new in Version 6.1.0.7 and it may not be present in a server which was upgraded. Restart the server after adding the property.

Data type Boolean
Default False (not selected)
ENABLE.ZOS.LP.RECOVERY [z/OS]

This property controls whether a listener port attempts to recover if a connection between the application server and WebSphere® MQ has been lost, for example if the queue manager has been stopped. Set this property to true to enable listener port recovery. This property is new in Version 6.1.0.16 and it might not be present in a server which was upgraded. Restart the server after adding the property.

Data type Boolean
Default False (not selected)
MAX.RECOVERY.RETRIES

The maximum number of times that a listener port managed by this service tries to recover from a failure before giving up and stopping. When stopped the associated listener port is changed to the stop state. The interval between retry attempts is defined by the RECOVERY.RETRY.INTERVAL custom property.

A failure can be one of two things:
  • An unexpected error has occurred when a listener port tries to get a message from the JMS provider.
  • The connection between the application server and the JMS provider has been lost, usually due to a network error.
Data type Integer
Units Retry attempts
Default 5
Range 0 (no retries) through 2147483647
MQJMS.POOLING.THRESHOLD

The maximum number of unused connections in the pool.

An MQSimpleConnectionManager allocates connections on a most-recently-used basis, and destroys connections on a least-recently-used basis. By default, a connection is destroyed if there are more than ten unused connections in the pool.

Data type Integer
Units Number of connections
Default 10
Range  
MQJMS.POOLING.TIMEOUT

The number of milliseconds after which a connection in the pool is destroyed if it has not been used.

An MQSimpleConnectionManager allocates connections on a most-recently-used basis, and destroys connections on a least-recently-used basis. By default, a connection is destroyed if it has not been used for five minutes.

Data type Integer
Units Milliseconds
Default 5 minutes
Range  
NON.ASF.BMT.ROLLBACK.ENABLED

When the non-Application Server Facilities (non-ASF) mode of operation is in use, and a message-driven bean using bean-managed transactions generates a runtime exception, this property determines whether messages are returned to the destination.

When this property is set to false (default), the message is automatically acknowledged before it is passed to the message-driven bean.

When this property is set to true, the message listener service sends a message acknowledgement to the client after the message is successfully processed by the message-driven bean, and the message listener service requests recovery of any message for which the bean generates an exception.

Note: The message listener service has two modes of operation, Application Server Facilities (ASF) and non-Application Server Facilities (non-ASF):
  • ASF mode provides concurrency and transactional support for applications. For publish/subscribe message-drive beans, ASF mode provides better throughput and concurrency, because in the non-ASF mode the listener is single-threaded.
  • Non-ASF mode is mainly for use with third-party messaging providers that do not support JMS ASF, which is an optional extension to the JMS specification. Non-ASF mode is also transactional but, because the path length is shorter than for ASF mode, usually provides improved performance.
Use non-ASF mode under the following circumstances:
  • Your third-party messaging provider does not provide JMS ASF support.
  • You are using message-driven beans with WebSphere topic connections with the DIRECT port, because the embedded publish/subscribe broker using that port does not support XA transactions or JMS ASF.
  • Message ordering is a strict requirement.
Data type Boolean
Default False
NON.ASF.RECEIVE.TIMEOUT

The timeout in milliseconds for synchronous message receives performed by message-driven bean listener sessions in the non-ASF mode of operation.

Set this property to a non-zero value only if you want to enable the non-ASF mode of operation for all message-driven bean listeners on the application server.

Note: The message listener service has two modes of operation, Application Server Facilities (ASF) and non-Application Server Facilities (non-ASF):
  • ASF mode provides concurrency and transactional support for applications. For publish/subscribe message-drive beans, ASF mode provides better throughput and concurrency, because in the non-ASF mode the listener is single-threaded.
  • Non-ASF mode is mainly for use with third-party messaging providers that do not support JMS ASF, which is an optional extension to the JMS specification. Non-ASF mode is also transactional but, because the path length is shorter than for ASF mode, usually provides improved performance.
Use non-ASF mode under the following circumstances:
  • Your third-party messaging provider does not provide JMS ASF support.
  • You are using message-driven beans with WebSphere topic connections with the DIRECT port, because the embedded publish/subscribe broker using that port does not support XA transactions or JMS ASF.
  • Message ordering is a strict requirement.
Data type Integer
Units Milliseconds
Default ASF mode (custom property not created)
Range 0 or greater milliseconds
0
non-ASF mode is disabled
1 or more
The timeout in milliseconds for non-ASF message-driven bean listener synchronous session receives
Recommended If a transaction timeout occurs, the message must recycle causing extra work. If you want to use the non-ASF mode, set this property to lower than the transaction timeout, but leave spare at least the maximum duration of your message-driven bean's onMessage() method. For example, if your message-driven bean's onMessage() method typically takes a maximum of 10 seconds, and the transaction timeout is set to 120 seconds, you might set the NON.ASF.RECEIVE.TIMEOUT property to no more than 110000 (110000 milliseconds, that is 110 seconds).
RECOVERY.RETRY.INTERVAL

The time in seconds between retry attempts by a listener port to recover from a failure. The maximum number of retry attempts is defined by the MAX.RECOVERY.RETRIES custom property.

A failure can be one of two things:
  • An unexpected error has occurred when a listener port tries to get a message from the JMS provider.
  • The connection between the application server and the JMS provider has been lost, usually due to a network error.
Data type Integer
Units Seconds
Default 60
Range 1 through 2147483647



Related tasks
Configuring the message listener service
Related reference
Message listener service properties
Reference topic    

Terms of Use | Feedback

Last updated: Feb 25, 2009 9:32:38 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/umb_prolscp.html