On Wed, Jul 23, 2014 at 10:48 AM, Stefan Egli <[email protected]> wrote: > ...I'm not sure yet what could cause this though...
There is some non-deterministic behavior at startup - as noted in SLING-3618 ClassLoaderWriterImpl seems to be part of the problem, that component is not immediate so we don't really know when it's activated. See the "A better way to create commonly used Resources at startup?" thread here for what I think is the core issue. -Bertrand
