ORDS on a "2 Node" Weblogic Cluster Fails to Deploy with Error "The je.lck file could not be locked..."
(Doc ID 2012339.1)
Last updated on FEBRUARY 18, 2021
Applies to:Oracle REST Data Services - Version 2.0.1 to 2.0.7
Information in this document applies to any platform.
Deploying the Apex Listener (ORDS) on a "2 node" Weblogic cluster fails to deploy with the error:
weblogic.application.ModuleException: : com.sleepycat.je.EnvironmentLockedException: (JE 4.0.103) <Shared_Area>/apex_listener/bdb The environment cannot be locked for single writer access. ENV_LOCKED: The je.lck file could not be locked. Environment is invalid and must be closed.
This is not a problem on a single node install.
The ORDS seems to deploy okay. The error is shown when the application is started. ORDS, however, does change from a state of prepared to Active.
This seems to be a problem with deploying to a Redhat GFS disk. If you relax the GFS file locking and let the NFS layer handle the locking, you don't get this problem.
If you use OCFS on OEL5, you don't get this problem. OCFS is not available on Redhat 6.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document