Flipping deployment.expiration.check.enabled from true->false has cache effect

XMLWordPrintable

      deployment.expiration.check.enabled=true from deployment config file has effect only after first applet launch. This happens because plugin do expiration check on native level and read the flag from a native cache, but the native cache is synchronized on java level after expiration check. Hence we have java expiration warning even if we have deployment.expiration.check.enabled=true

            Assignee:
            Mikhail Cherkasov (Inactive)
            Reporter:
            Abhijit Saha
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: