Caching EJB3 remote references prevents pooling or not?
posted 5 years ago
I have a client application that uses EJB3 beans by remote lookup. For performance reasons I cache the remote references in a map.
Now does this force the client application to always use the same EJB3 instance as same reference is used again and again or does EJB pooling still works and returns other instances from the pool for requests handling?
The application server I am using is JBoss 5.1.