Problem With Clustering of Hibernate Sessionfactory Across Managed Servers

(Doc ID 1269192.1)

Last updated on NOVEMBER 09, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.3 and later
Information in this document applies to any platform.

Symptoms

In the WebLogic managed server logs, following errors are noticed related to Hibernate’s SessionFactory is a NON CLUSTERABLE object.

####<Nov 16, 2010 8:34:05 AM CST> <Error> <Cluster> <epsun647> <M2> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1289918045285> <BEA-000123> <Conflict start: You tried to bind an object under the name HibernateSessionFactory in the JNDI tree. The object from 4449434054399910424S:epsun674.custServer.com:[8001,8001,-1,-1,-1,-1,-1]:epsun646.custServer.com:8001,epsun647.custServer.com:8001,epsun674.custServer.com:8001:EAPPTESTWLS103:M3 is non-clusterable, and you have tried to bind more than once from two or more servers. Such objects can only be deployed from one server.>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms