Uploaded image for project: 'Commons Pool'
  1. Commons Pool
  2. POOL-221

PooledObject.state does not need to be volatile

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0
    • Labels:
      None

      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().

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              sebb Sebb
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: