Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JNDI Lookup & Caching issue on multiple BEA instances

 
Joe Harry
Ranch Hand
Posts: 10085
3
Eclipse IDE Mac PPC Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Guys,

I have a scenario where in upon application start up (of my client) I do a look up on different BEA instances (physical servers). I have a Value Object that stores the cached remote reference. Thus I have a class that holds the List of these two Value Objects. Now my clients make a call to a method in the remote facade using the cached remote reference in the Value Object. Following that I undeploy the EJB's in one of the BEA server and try to call a method with the cached remote reference. As per the EJB specification, expected is a NoSuchEJBException, but I'm getting some strange exception as below:



I perform the JNDI lookup on the different servers during initialization of my Service Dispatcher (happens only once): The client will call new ServiceDispatcher
constructor with the necessary parameters as shown below in the code.



The ServiceInstance is just a Value Object and the JNDI LookUp method is as below:




Baffled with the exception that Weblogic throws. Below is how my client call looks like:




 
Deepak Bala
Bartender
Posts: 6663
5
Firefox Browser Linux MyEclipse IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So you want to confirm if the spec is followed correctly ? Sounds like a case to raise a ticket with BEA ?
 
Joe Harry
Ranch Hand
Posts: 10085
3
Eclipse IDE Mac PPC Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is this an issue with BEA? Or is it a design issue with what I have done.
 
Deepak Bala
Bartender
Posts: 6663
5
Firefox Browser Linux MyEclipse IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A close look at the exception suggests that the work manager behind the EAR application by itself has shutdown ?

Have you tried undeploying the EJBs alone ?
 
Joe Harry
Ranch Hand
Posts: 10085
3
Eclipse IDE Mac PPC Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What I did was just to stop the EAR application and then tried to access the remote facade with the cached reference. Later I even un deployed the EJB's but even after that I keep getting this same exception message.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic