[POOL-221] PooledObject.state does not need to be volatile

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0
• Assignee: Unassigned
• Reporter: Sebb
• Created: 05/May/12 01:17
• Updated: 31/Dec/14 16:24
• Resolved: 05/May/12 20:59

Description

The field PooledObject.state is volatile, but is also always accessed in a synchronised method except in toString().

The volatile modifier is not cost free; it might be better to remove it and add a small synch. block in toString().