A listener port is used to simplify administration of the association between a connection factory, destination, and deployed message-driven bean.
Use this panel to view or change the configuration properties of the selected listener port.
To view this administrative console page, click
application_server listener_portThe name by which the listener port is known for administrative purposes.
Data type | String |
Default | Null |
The state that you want the listener port to have when the application server is next restarted
Data type | Enum |
Units | Not applicable |
Default | Started |
Range |
|
A description of the listener port, for administrative purposes within IBM WebSphere Application Server.
Data type | String |
Default | Null |
The JNDI name for the JMS connection factory to be used by the listener port; for example, jms/connFactory1.
Data type | String |
Default | Null |
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.
Data type | String |
Default | Null |
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 and if you do not need to process messages in a specific message order.
Data type | Integer |
Units | Sessions |
Default | 1 |
Range | 1 through 2147483647 |
Recommended |
|
The maximum number of times that the listener tries to deliver a message before the listener is stopped, in the range 0 through 2147483647.
Every message has a delivery count associated with it, which is incremented if the message cannot be delivered, or is delivered successfully to a message-driven bean instance and then rolled back. When the delivery count of a message equals the value of this property, the listener is stopped.
Data type | Integer |
Units | Retry attempts |
Default | 0 (no retries) |
Range Recommended |
0 (no retries) through 2147483647. When using WebSphere MQ as the JMS provider, this property should be greater than the value of the WebSphere MQ queue property Backout threshold (BOTHRESH). This allows WebSphere MQ to remove the message from the queue without the need to shut down the listener. |
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 the WebSphere V5 default messaging provider or WebSphere MQ as the JMS provider, if messages start accumulating on the queue then the listener can start processing messages in batches. For generic JMS providers, this property value is passed to the JMS provider but the effect depends on the JMS provider.
Data type | Integer |
Units | Number of messages |
Default | 1 |
Range | 1 through 2147483647 |
Recommended | For the WebSphere default messaging providers or 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 overhead of transactions
on JMS messages.
CAUTION:
|