[POOL-46] [pool] BaseObjectPool closed boolean field needs to be volatile

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2
• Fix Version/s: 1.3

Environment

Operating System: All
Platform: All

• Bugzilla Id: 38690
• Assignee: Unassigned
• Reporter: Sandy McArthur (from Bugzilla import)
• Created: 17/Feb/06 09:34
• Updated: 12/Sep/10 17:42
• Resolved: 12/Sep/10 17:42

Description

The private field 'closed' in BaseObjectPool needs to be volatile because in a
multi-threaded environment sub-classes that don't synchronize access before
calling isOpen() (or asserOpen()) may not see changes to this value in a timely
manner.

In leu of attaching a patch I'll just show the correct declaration for line 82:

private volatile boolean closed = false;