|
Problem |
By default, the JMS Listener included with WebSphere® EE
can process only one JMS session at a time. This is a problem if the
business logic that is called when a message is received from the JMS
destination hangs. In this case, the listener is unable to process other
sessions. |
|
Solution |
Increase the MaxSessions parameter in the extended
messaging configuration file. This property is the maximum number of
sessions that the listener can have with the destination that it is
monitoring.
The number of sessions must be a positive integer; the default is
1.
|
|
|
|
|
|
|