My application is designed around Session facade(Session facade id CMT session bean) in each method user gets Hibernate session and after he is done with it(mothod) session is closed in "finally" (this includes session.flush(); session.close()).

In cluster few issues raise, how do I work with the same Hibernate session thru the transaction(which could be distributed) if one Session facade decides to call another and how do I rollback since each facade is managing its own Hibernate session.

Is there away?

Thanks.

Michael.

This may not be a viable solution but you can avoid the clusering issue by layering your architecture. The session facade can be considered the service layer and as such the start and finish of the transaction (usually using CMT). This layer communicates only to lower layers or with hibernate directly, if you find other service layer methods are required by the current service layer then you refactor the code and move the common code into a DAO layer where both service methods now use the DAO layer services. The service layer (optionally) communicates the hibernate session through a thread local so everthing is nice and clean.

How about if the service layer makes a remote call to another service layer component (EJB) which resides on a different physical machine in a cluster? Will thread local still work?