java.lang.ExceptionInInitializerError

This exception has no message.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web8203

  • This exception has no message.
  • This exception has no message.
  • via Terracotta by acs, 11 months ago
    This exception has no message.
  • Stack trace

    • java.lang.ExceptionInInitializerError at com.zextras.lib.ZENotificationStore.<init>(Unknown Source) at com.zextras.lib.ZENotifier.<init>(Unknown Source) at com.zextras.lib.ZECore.<init>(Unknown Source) at com.zextras.lib.ZECore.getInstance(Unknown Source) at com.zextras.extension.ZExtrasExtension.postInit(Unknown Source) at com.zimbra.cs.extension.ExtensionUtil.postInitAll(ExtensionUtil.java:149) at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:270) at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:123) at com.zimbra.soap.SoapServlet.init(SoapServlet.java:128) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:440) at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:685) at org.mortbay.jetty.servlet.Context.startContext(Context.java:140) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1254) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:471) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.handler.DebugHandler.doStart(DebugHandler.java:127) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.Server.doStart(Server.java:224) at org.mortbay.setuid.SetUIDServer.doStart(SetUIDServer.java:158) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.mortbay.start.Main.invokeMain(Main.java:194) at org.mortbay.start.Main.start(Main.java:534) at org.mortbay.start.Main.start(Main.java:441) at org.mortbay.start.Main.main(Main.java:119) Caused by: java.lang.NullPointerException at com.zextras.lib.ZEConfig.get(Unknown Source) at com.zextras.lib.ZENotificationStore.<init>(Unknown Source) at com.zextras.lib.ZENotifier.<init>(Unknown Source) at com.zextras.lib.ZECore.<init>(Unknown Source) at com.zextras.lib.ZECore.getInstance(Unknown Source) at com.zextras.lib.ZECore.getNotifier(Unknown Source) at com.zextras.lib.ZENotifier.getInstance(Unknown Source) at com.zextras.lib.ZENotifier.notify(Unknown Source) at com.zextras.lib.ZENotifier.notify(Unknown Source) at com.zextras.lib.ZEConfig.load(Unknown Source) at com.zextras.lib.ZEConfig.<clinit>(Unknown Source) ... 42 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.