Record Locks Prevent User From Logging Into EDM Application From Any Workstation
(Doc ID 759136.1)
Last updated on FEBRUARY 01, 2022
Applies to:
Oracle Agile Engineering Data Management - Version 5.0.1 to 6.1.2.2 [Release 5.0.0 to 6.1.0]Information in this document applies to any platform.
Symptoms
SYMPTOM #1
After a server crash, a specific user cannot log into the application or is unable to perform a certain function or is hampered by unusual behavior in the Client. The issue follows the user when logging in from other workstations.
SYMPTOM#2
Receive error message, "Record {Record Name} is currently locked by user {PLM <USERNAME>}".
SYMPTOM#3
Java client trace has the following error: com.agile.eci.ConnectionException: Server terminated with exit code 134 [err=102]
SYMPTOM#4
ERROR
INFO 05/15/18 09:05:53 [EciDaemonThread-648122] - Request nr: 1001
INFO 05/15/18 09:05:53 [EciDaemonThread-648121] - [AxalantServer] Trying to open administrative connection
INFO 05/15/18 09:05:53 [EciDaemonThread-648122] - [EciDaemonThread] Thread terminating
WARN 05/15/18 09:05:54 [EciDaemonThread-648121] - [EciCon] Caught java.io.IOException: IpcBytePacketReader.readBlock: Unexpected end of stream (0/11) while waiting for answer
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| Procedure#1 - Removing Locks on the Database for a Specific User |
| Procedure#2 - Checking for Orphaned Locked Records on the Application Server |
| References |