Listener port settings
A listener port defines the association between a connection factory, a destination, and a deployed message-driven bean. This association enables deployed message-driven beans associated with the port to retrieve messages from the destination.
Use this panel to view or change the configuration properties of the selected listener port.
To view this administrative console page, click .
Name
The name by which the listener port is known for administrative purposes.
Information | Value |
---|---|
Data type | String |
Default | Null |
Initial state
The state that you want the listener port to have when the application server is next restarted
Information | Value |
---|---|
Data type | Enum |
Units | Not applicable |
Default | Started |
Range |
|
Description
A description of the listener port, for administrative purposes within IBM® WebSphere® Application Server.
Information | Value |
---|---|
Data type | String |
Default | Null |
Connection factory JNDI name
The JNDI name for the JMS connection factory to be used by the listener port; for example, jms/connFactory1.
Information | Value |
---|---|
Data type | String |
Default | Null |
Destination JNDI name
The JNDI name for the destination to be used by the listener port; for example, jms/destn1.
You cannot use a temporary destination for late responses.
Information | Value |
---|---|
Data type | String |
Default | Null |
Maximum sessions
The maximum number of concurrent sessions that a listener can have with the JMS server to process messages.
Each session corresponds to a separate listener thread and therefore controls the number of concurrently processed messages. Adjust this parameter when the server does not fully use the available capacity of the machine.
Information | Value |
---|---|
Data type | Integer |
Units | Sessions |
Default | 1 |
Range | 1 through 2147483647 |
Recommended |
|
Maximum retries
The maximum number of times that the listener tries to deliver a message to a message-driven bean instance before the listener is stopped, in the range 0 through 2147483647.
- If you exceed the WebSphere MQ queue BackoutThreshold limit, the message that cannot be delivered is moved to somewhere else by WebSphere MQ (for example, to the WebSphere MQ backout requeue queue or the WebSphere MQ dead letter queue) and the listener port services the next message on the queue. In this case, WebSphere Application Server might not know that the message has not been delivered successfully.
- If you exceed the listener port maximum retries limit, the listener port stops. You then manually intervene to investigate the problem, possibly to remove the message from the WebSphere MQ queue then restart the listener port.
Information | Value |
---|---|
Data type | Integer |
Units | Retry attempts |
Default | 0 (no retries) |
Range | 0 (no retries) through 2147483647 |
Maximum messages
The maximum number of messages that the listener can process in one transaction.
If the queue is empty, the listener processes each message when it arrives. Each message is processed within a separate transaction.
For WebSphere MQ as the JMS provider, if messages start accumulating on the queue then the listener can start processing messages in batches. For third-party messaging providers, this property value is passed to the JMS provider but the effect depends on the JMS provider.
Information | Value |
---|---|
Data type | Integer |
Units | Number of messages |
Default | 1 |
Range | 1 through 2147483647 |
Recommended |
For WebSphere MQ as the JMS provider, to process
multiple messages in a single transaction, set this value to more than 1. If messages start
accumulating on the queue, a value greater than 1 enables multiple messages to be batch-processed
into a single transaction, and eliminates much of the transaction processing costs for JMS
messages.
CAUTION:
|