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 Servers-> Application Servers-> application_server-> Message Listener Service-> Listener Ports-> listener_port
Data type | String |
Default | Null |
Data type | Enum |
Units | Not applicable |
Default | Started |
Range |
|
Data type | String |
Default | Null |
Data type | String |
Default | Null |
If the extended messaging service is to use this listener port to handle late responses, the value of this property must match the JMS response destination on the output port used by the sender bean.
You cannot use a temporary destination for late responses.
Data type | String |
Default | Null |
Each session corresponds to a separate listener thread and therefore controls the number of concurrently processed messages. Adjust this parameter when the JMS 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 to a message-driven bean instance before the listener is stopped.
Data type | Integer |
Units | Retry attempts |
Default | 0 (no retries) |
Range | 0 (no retries) through 2147483647 |
If the queue is empty, the listener processes each message when it arrives. Each message is processed within a separate transaction.
For the WebSphere embedded messaging 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 embedded messaging or WebSphere MQ as the JMS provider, if you want to process multiple messages in a single transaction, then set this value to more than 1. If messages start accumulating on the queue, then 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. Note:
|