This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes EJB and other Java EE Technologies and the fly likes problem encountered with clustering Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "problem encountered with clustering" Watch "problem encountered with clustering" New topic
Author

problem encountered with clustering

binu sukumar
Greenhorn

Joined: Aug 07, 2001
Posts: 7
Hi,
We are using ejb on Weblogic server with clustering. For stateful session beans,handle (javax.ejb.Handle) is stored in HttpSession and is reactivated whenever needed.
Problem is, when we stop one of the servers and run the application, handle reactivation is giving error.(NoSuchObject).
It seems, the handle is specific to one server instance of the cluster ,other server instances are not aware of this handle.
Any suggestions to solve this..,
Is this a set up issue..?
Anonymous
Ranch Hand

Joined: Nov 22, 2008
Posts: 18944
AFIK, you should chache the Remote interface and not the handle. Handle is supposed to be container specific and Remotes (& homes) are clusterable.
 
 
subject: problem encountered with clustering