Issue Details (XML | Word | Printable)

Key: NUCCORE-1138
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Kaarel Kann
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
DataNucleus Core

L2 cache configuration not reset when getting ExecutionContext from pool

Created: 25/Feb/14 10:54 AM   Updated: 01/Mar/14 07:39 PM   Resolved: 25/Feb/14 02:49 PM
Component/s: Cache
Affects Version/s: 3.2.12
Fix Version/s: 3.2.13, 4.0.0.m1

File Attachments: 1. Java Source File SimpleTest.java (2 kB)

Environment: Any

Severity: Development


 Description  « Hide
Documentation says that PersistenceManager L2 cache can be different from PersistenceManagerFactory conf (i.e it can be disabled per PM), but ExecutionContext pooling breaks this feature as L2 cache configuration is not reset when getting EC from pool.



Kaarel Kann added a comment - 25/Feb/14 10:57 AM
Attached testcase.
Can be downloaded: https://github.com/kaarelk/test-jdo/tree/l2cache_ec-cache

Kaarel Kann made changes - 25/Feb/14 10:57 AM
Field Original Value New Value
Attachment SimpleTest.java [ 12049 ]
Andy Jefferson made changes - 25/Feb/14 12:08 PM
Comment [ Dont see how your test shows anything. You open a PM, set it to not use the L2 cache, and then close it. So the PM which isn't using the L2 cache is now closed. Any new PM will use what the PMF has. ]
Kaarel Kann added a comment - 25/Feb/14 01:41 PM

Andy Jefferson made changes - 25/Feb/14 02:49 PM
Status Open [ 1 ] Resolved [ 5 ]
Fix Version/s 3.2.13 [ 12100 ]
Fix Version/s 4.0.0.m1 [ 12081 ]
Resolution Fixed [ 1 ]
Andy Jefferson made changes - 01/Mar/14 07:39 PM
Status Resolved [ 5 ] Closed [ 6 ]