EJB Container (WebSphere 7) doesn't contain all the EJB references

[Sonx Nkuks]

Hi, our ibm-ejb-jar-bnd.xml containes quite a number of session beans with remote/local references. I noticed that not all of them are loaded to the container. I see this when i open ejb references on websphere admin console within the application. Aslo, if i deploy the application using the workspace it takes forever, but installing it through admin console gets through successfully, except the above. Is this caused by the cache size or bean allowed in the session?

[Claude Moore]

Hi, I don't remember seeing such a behaviour in WAS.... Did you try to open a PMR ? Moreover, did you try as workaround to split your EJB project in two or three EJB project, in order of reducing xml descriptor size and entries number ?

[Sonx Nkuks]

Claude Moore wrote:Hi, I don't remember seeing such a behaviour in WAS.... Did you try to open a PMR ? Moreover, did you try as workaround to split your EJB project in two or three EJB project, in order of reducing xml descriptor size and entries number ?

Hi Claude, i opened the ibm-ejb-jar-bnd.xml and noticed that remote beans are referenced in two ways, using <interface /> tag and others <ejb-ref /> tag... In our architect design the <interface /> references the session facade EJBs and <ejb-ref> to Business objects EJBs (BOBeans). Only the BOBeans referenced with <ejb-ref> are visible under ejb-references in my app on admin console. Mine is mapped using <interface />

[Claude Moore]

Hi Sonx,

well, to be quite honest I used to use WAS 6.1 and now i'm going deep into WAS 8, so I'm not very expert on WAS 7... nevermind, websphere versions are very well retro-compatibles, so I think that there would be not many differences in deployment descriptors...
Now, with wich IDE do you develop your EJBs ? Do you use Rational ? If yes, what happens if your validate your ejb project ? If you open with the visual editor the ejb.xml (with 'visual editor' i mean the prospective that help you in seeing declared ejbs, interfaces, transactional behaviour and so on) can you see the missing ejbs ?