JavaRanch » Java Forums »
Products »
BEA/Weblogic
| Author |
JNDI Lookup & Caching issue on multiple BEA instances
|
Joe Harry
Ranch Hand
Joined: Sep 26, 2006
Posts: 8795
|
|
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:
|
SCJP 1.4, SCWCD 1.4 - Hints for you, SCBCD Hints - Demnachst, SCDJWS - Auch Demnachst
Did a rm -R / to find out that I lost my entire Linux installation!
|
 |
Deepak Bala
Bartender
Joined: Feb 24, 2006
Posts: 6588
|
|
|
So you want to confirm if the spec is followed correctly ? Sounds like a case to raise a ticket with BEA ?
|
SCJP 6 articles - SCJP 5/6 mock exams - SCJP Mocks - SCJP 5 Mock exam (Word document ) - SCJP 5 Mock exam in Java.Inquisition format
|
 |
Joe Harry
Ranch Hand
Joined: Sep 26, 2006
Posts: 8795
|
|
|
Is this an issue with BEA? Or is it a design issue with what I have done.
|
 |
Deepak Bala
Bartender
Joined: Feb 24, 2006
Posts: 6588
|
|
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
Joined: Sep 26, 2006
Posts: 8795
|
|
|
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.
|
 |
 |
|
|
subject: JNDI Lookup & Caching issue on multiple BEA instances
|
|
|
|