Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-7131655

Atomic*FieldUpdater security permissions too strict

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Duplicate
    • Affects Version/s: 7
    • Fix Version/s: None
    • Component/s: core-libs
    • Labels:
      None

      Description

      The use of Atomic*FieldUpdater.newUpdater is restricted by security policy. This creates a problem when using java.util.concurrent in applets. It should be possible to create updaters for fields accessible from the scope of the caller, without a security policy change.

      For example, a static class initializer should be able to create field updaters for any fields in the same class, because the same fields could be accessed or modified by any methods in the same class anyway.

      A reproducer is a trivial call to AtomicLongFieldUpdater.newUpdater in the static initializer for an existing private field of the class. Class loading fails, when used within applet.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ootenko Oleksandr Otenko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: