|
If you were logged in you would be able to see more operations.
|
|
If a repository connection changed the state of the store and was later lost (garbage collected), subsequent calls to getConnection will block indefinitely without any indication as what is happening, and often preventing any further diagnoses. This can be a significant barrier for development teams with less Java coding skills.
Although, the use of finalize methods has shown to add significant overhead to the garbage collector, the use of WeakReference to active locks should allow the lock manager to detect active locks that have been lost, without declaring finalize methods on every lock object.
|
|
Rewrite the lock manager in revision 11806 to always track all active locks using WeakReferences and check periodically for abandoned locks.
|
|
Improvement
Resolved
Major
Recovery From Abandoned Connections