Re: Cannot look up EJB deployed to different managed server
in same

Hi Sabrina,

Thanks for taking the time to respond. I understand now the problem with the
pinned EAR and the URL for the jndi lookup.

I think I also understand the reason why it is happening with the EAR targetted
at the cluster. It appears that the EAR fails to initialise properly on one of
the managed servers. An instance variable in a Stateless Session Bean is
throwing a RuntimeException. From the WebLogic console it appears that the EAR
has deployed however if you drill down to the EJBs you see that it's only
deployed on one of the managed servers. I've changed my code to initialise the
instance variable in one of the EJB methods.

I need to do further testing to verify that this will fix it but initial
indications are looking good. I would have expected a deployment error in the
WebLogic managed server logs.

Thanks again,