>I looked at the examples in the standardjboss.xml and the Stateless Session Beans had no configurations regarding timeouts
Instances of stateless session beans are managed in a pool of the container.
When you call a method to a stateless session bean, one comes from the pool and after the method returns the instance goes back to the pool.
With this pool, the server can handle more beans than actual number of instances.
It can be done because they are 'stateless'.
Thus you have no way to keep the same instance on the server side while your application uses it.
This is my understanding why we cannot set the timeout to them.
I understand what you are saying but if the Bean does not return and is waiting on some call to complete, I would like to force the timeout myself and allow the Bean to be recycled in the pool.
I understant your point of view but what if
"the method does not return" I would like the Bean to time out after some time
> When you call a method to a stateless session bean,
> one comes from the pool and after the method returns
> the instance goes back to the pool.
If my method does not return I would like the Bean to timeout after some time