CODEWITHSUNDEEP
javajndiejb-3.0stateful-session-beansession-bean
SacJn
SacJn

Reputation: 777

Storing EJB 3 Session Bean references into Map

Currently I am using EJB3.0 session beans in my application. Normally i lookup the bean using jndi name and call the concerned method. But recently what I was suggested to store these references in a Map rather than looking up again and again.

Is this a good practice to store Session Bean references into Map to avoid their lookup every time ? Or is it Hazardous ? What kind of problems if at all application may have to encounter ?

If it is a good practice then I have another concern.

Class that contains Map to store references is part of Module A. While session beans are part of Module B1 ...Bn. So Once after looking up when I store the reference in Map, I can retrieve it back. In the meantime Module Bn is redeployed but A remains as it is. So now after looking up the bean from the Map ( as it contains entry) using it, ClassCast Exception is thrown.

What is the reason of that and how can I avoid ? I am using JBOSS Application server - jboss 5.1.0.GA

Upvotes: 2

Views: 535

Answers (1)

Brett Kail
Brett Kail

Reputation: 33936

It is fine to cache references to stateless and singleton session bean lookups. That's basically what the @EJB annotation does when you use it on a field. (It obviously does not work for stateful session beans, which return a distinct EJB reference for each lookup.)

You didn't mention your application server and didn't provide a stack trace for the ClassCastException, but restarting a module very likely creates a new class loader for the new instance of the application, which means the EJB references that you have cached are now incompatible. I would have guessed a similar ClassCastException would happen even if you didn't cache the result, but perhaps your application server has a workaround for that. It's probably best to restart all caller modules (or just the entire application) when restarting EJB modules.

Upvotes: 1

Related Questions