Java Reference
In-Depth Information
stance. After an MDB instance's
onMessage()
method returns, the request is com-
plete, and the instance is placed back in the free pool. This results in the best re-
sponse time, as the request is served without waiting for a new instance to be cre-
ated.
Note
On the other hand, if all instances in the pool are busy, the new request will be
serialized, since it's guaranteed that the same instance will not be allowed to
serve multiple clients at the same time. Also, if a client sends out multiple mes-
sages to the server containing an MDB, there is no guarantee the same MDB
instance will be used for each message or that the messages will be processed
in the same order the client sent them. This means that the application should be
designed to handle messages arriving out of order.
The amount of MDB in the pool is configured in the EJB pool, which can be reached
from the console by going to
Profile
|
Container
|
EJB 3
:
