misc catchup (original) (raw)

Doug Lea dl at cs.oswego.edu
Fri Nov 2 13:28:11 PDT 2012

On 11/01/12 07:53, Doug Lea wrote:

This deserves some attention. If the static-init occurs from the context of an unprivileged thread, we probably still want to create it in some default form. Further, if that thread tries to use it, then invokes etc will still work, without creating any workers ...

Doing this out leads to a policy issue. If the static initialization of commonPool occurs from an unprivileged, and thus the Property gets and newInstance's (of factory or handler) fails, then we have some choices:

  1. Ignore all the exceptions and create with defaults

  2. Same as (1) plus log some kind of message, in case decoding props etc just showed a dumb mistake, not a security, class-loader, etc problem.

  3. Abort construction, in which case all the lambda-lib stuff will fail or act strangely for everyone else too.

For now I'm doing (1).

-Doug

More information about the lambda-libs-spec-observers mailing list