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
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 FixPack 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) |
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 FixPack 6.1.0.16 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) |
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.
Data type | Integer |
Units | Retry attempts |
Default | 5 |
Range | 0 (no retries) through 2147483647 |
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 |
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 |
Whether messages should be returned to the destination after a message-driven bean using bean-managed transactions throws a runtime exception and the non-Application Server Facilities (non-ASF) mode of operation is in use.
When the NON.ASF.BMT.ROLLBACK.ENABLED property is set to false (default), the message is automatically acknowledged before the message is passed to the message-driven bean.
When this property is set to true, the message listener service performs client acknowledgement of each message after it is successfully processed by the message-driven bean, and requests recovery of messages for which the bean generates an exception.
Data type | Boolean |
Default | False |
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.
Data type | Integer |
Units | Milliseconds |
Default | ASF mode (custom property not created) |
Range | 0 or greater milliseconds
|
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). |
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.
Data type | Integer |
Units | Seconds |
Default | 60 |
Range | 1 through 2147483647 |