Chapter 5. Performance tuning 123
5.3.2 Stateless connections
The majority of call.connect beans and all vendor.connect beans are common stateless
session beans and use stateless connections. One method call (typically one interaction
between the client and the server) obtains a stateless connection from the WebSphere
datasource, performs the necessary work, and then returns the connection to the pool.
If all clients would execute a method at exactly the same time, then you would need one
connection per client. A single call.connect client sometimes obtains two independent
connections for reasons of transaction boundaries.
In an extreme case, the number of stateless connections required could be twice the number
of clients. However in practice, ...