Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/Bugs/259993
< EclipseLink | Bugs
Revision as of 22:45, 15 January 2009 by Unnamed Poltroon (Talk) (New page: = Bug Analysis Document: 259993: Deadlock on em.find() on WebSphere 7.0.0.1= * [http://bugs.eclipse.org/259993 Bugzilla Bug 259993] == Document History == {|{{BMTableStyle}} |-{{BMTHStyl...)
Contents
- 1 Bug Analysis Document: 259993: Deadlock on em.find() on WebSphere 7.0.0.1
Bug Analysis Document: 259993: Deadlock on em.find() on WebSphere 7.0.0.1
Document History
Date | Author | Version Description & Notes |
---|---|---|
20080115 | Michael O'Brien | 1.0 Initial reproduction use cases |
Overview
This bug describes the behavior and fix for an isssue where an em.find() on WebSphere 7.0.0.1 hangs indefinitly when attempting to acquire lock on the concurrencyManager on a cacheKey.
Concepts
JPA Specification Notes
JPA 1.0 Specification
JPA 2.0 Specification
Reproduction
Prerequisites
Data Model
Use Case 1: Persist unmanaged entity (with @PrePersist query) referenced by managed entity
StackTrace
Logs
Analysis Constraints
Concurrency and Thread Safety
Design / Functionality
Alternative 1:
Implementation
Logging
Testing
API
GUI
Config files
Documentation
Open Issues
Issue # | Owner | Description / Notes |
---|---|---|
I1 | mobrien | - |
Decisions
Issue # | Description / Notes | Decision |
---|---|---|
Future Considerations
During the research for this bug, the following items were identified as out of scope but are captured here as potential future enhancements. If agreed upon during the review process these should be logged in the bug system.