Are you using jetty-logging.properties as well? -- Joakim Erdfelt <[email protected]> webtide.com <http://www.webtide.com/> - intalio.com/jetty Expert advice, services and support from from the Jetty & CometD experts eclipse.org/jetty - cometd.org
On Mon, Apr 28, 2014 at 2:37 AM, MILLON, YVES (YVES) < [email protected]> wrote: > Hi, > > Sometimes, on some hardware, we got exceptions at startup due to NPE in > the class "Log.java": > > Caused by: java.lang.NullPointerException > at org.eclipse.jetty.util.log.Log.getLogger(Log.java:288) > at org.eclipse.jetty.util.log.Log.getLogger(Log.java:271) > at > > org.eclipse.jetty.websocket.jsr356.server.BasicServerEndpointConfigurator.<clinit>(BasicServerEndpointConfigurator.java:34) > ... 54 more > > Caused by: java.lang.NullPointerException > at org.eclipse.jetty.util.log.Log.getLogger(Log.java:288) > at org.eclipse.jetty.util.log.Log.getLogger(Log.java:271) > at > > org.eclipse.jetty.security.authentication.LoginAuthenticator.<clinit>(LoginAuthenticator.java:38) > ... 13 more > > It seems that the method "Log.initialized()" is not fully thread safe > because the default logger is set outside of the synchronized block. > > Regards, > Yves > > > > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
