A fix is available
APAR status
Closed as program error.
Error description
Rational Application developer 7.5.4 and Rational Software Archi tect 7.5.4, a hang (deadlock) is encountered when refactoring Ja va and JSP files.
Local fix
Problem summary
The analysis of the Java Cores taken during the hang, shows that there are two threads related to the Link Indexer. One thread has a lock on one resource, but it is parked: Thread Name : main State : Parked Owns Monitor Lock on com/ibm/etools/references/internal/management/Link@0x1CDAD7F 8/0x1CDAD804 Java Stack : at sun/misc/Unsafe.park(Native Method) at java/util/concurrent/locks/LockSupport.park(Bytecode PC:14(Compiled Code)) at java/util/concurrent/locks/AbstractQueuedSynchronizer.parkAn dCheckInterrupt(Bytecode PC:1(Compiled Code)) at java/util/concurrent/locks/AbstractQueuedSynchronizer.doAcqu ireShared(Bytecode PC:1(Compiled Code)) at java/util/concurrent/locks/AbstractQueuedSynchronizer.acquir eShared(Bytecode PC:10(Compiled Code)) at java/util/concurrent/locks/ReentrantReadWriteLock$ReadLock.l ock(Bytecode PC:10(Compiled Code)) at com/ibm/etools/references/internal/index/ReferenceDatabase.g etInternalReferenceRecord(Bytecode PC:10(Compiled Code)) The other thread is blocked because it requires a lock on the same resource. Thread Name : org.eclipse.jdt.internal.ui.text.JavaReconciler State : Blocked Waiting for Monitor Lock on com/ibm/etools/references/internal/management/Link@0x1CDAD7F 8/0x1CDAD804 Java Stack : at com/ibm/etools/references/internal/index/ReferenceDatabase.d bUpdateRecord(Bytecode PC:212(Compiled Code)) at com/ibm/etools/references/internal/index/ReferenceDatabase.a ssignAndUpdate(Bytecode PC:89(Compiled Code))
Problem conclusion
This problem was caused by Link Indexer database locks getting in the way of the Link Indexer string database. In v754 strings were stored in the same database as the artifacts and they shared locks. This required careful coding to avoid deadlocks such as this one. As of V7551, this problem is completely gone because strings are stored in a separate database with separate locks. This means that it is possible to avoid deadlock issues between these two database entirely. Fix delivered in Rational Application Developer V7.5.5.1
Temporary fix
Comments
APAR Information
APAR number
PM05159
Reported component name
RATL APP DEV WI
Reported component ID
5724J1901
Reported release
754
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-14
Closed date
2010-04-01
Last modified date
2010-04-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
RATL APP DEV WI
Fixed component ID
5724J1901
Applicable component levels
R754 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 April 2010