OC4j: How to Resolve the sharing violation by ending the process currently holding the file lock or by using a different persistence directory for one or both processes

Introduction:

Requirement to configure additional OC4J instance for PDF printing for two different application.

Error:

ERROR ServerFile[PersistentMap,/u02/oc4j/j2ee/home/persistence/jms.state]: persistence file could not be locked. Resolve the sharing violation by ending the process currently holding the file lock or by using a different persistence directory for one or both processes.

Cause:
There are multiple OC4J processes in the same island. This could prevent the lock files being cleaned correctly during instance shutdown.

Workaround:
1. Ensure that there is no running OC4J instance that is accessing the persistence store.
2. Navigate to the “persistence” directory for the OC4J instance that fails to start.
3. Remove the “.lock” files. For example:

$ cd ${ORACLE_HOME}/j2ee
$ cd home/persistence
$ rm -f *.lock

Reference Doc ID 404942.1