Activiti

java.util.logging.ErrorManager/ NullPointerException in catalina.out at startup of tomcat

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.0.beta1
  • Fix Version/s: 5.0.beta2
  • Component/s: None
  • Labels:
    None
  • Environment:
    Mac OS X 10.6.4, Apache Tomcat/6.0.26, JVM 1.6.0_20-b02-279-10M3065
  • Number of attachments :
    0

Description

INFO: Deploying web application directory activiti-engine-init
java.util.logging.ErrorManager: 4
java.lang.NullPointerException
at org.apache.juli.FileHandler.openWriter(FileHandler.java:333)
at org.apache.juli.FileHandler.<init>(FileHandler.java:65)
at org.apache.juli.FileHandler.<init>(FileHandler.java:56)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at org.apache.juli.ClassLoaderLogManager.readConfiguration(ClassLoaderLogManager.java:515)
at org.apache.juli.ClassLoaderLogManager.readConfiguration(ClassLoaderLogManager.java:460)
at org.apache.juli.ClassLoaderLogManager$2.run(ClassLoaderLogManager.java:373)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.juli.ClassLoaderLogManager.getClassLoaderInfo(ClassLoaderLogManager.java:370)
at org.apache.juli.ClassLoaderLogManager.getLogger(ClassLoaderLogManager.java:224)
at java.util.logging.LogManager.demandLogger(LogManager.java:390)
at java.util.logging.Logger.getLogger(Logger.java:274)
at org.apache.juli.logging.DirectJDKLog.<init>(DirectJDKLog.java:71)
at org.apache.juli.logging.DirectJDKLog.getInstance(DirectJDKLog.java:178)
at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:171)
at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:316)
at org.apache.catalina.core.ContainerBase.getLogger(ContainerBase.java:387)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4352)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:519)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

Activity

Hide
Frederik Heremans added a comment -

Stacktrace told me something is wrong with the Formatter used on the Filehandler:

apache-tomcat-6.0.26-src -> org.apache.juli.FileHandler, line 333: writer.write(getFormatter().getHead(this));

The activiti-engine-init uses a custom Formatter, an inner class of LogUtil, LogUtil$LogFormatter.
Since beta1, the PVM is separated into another module and LogUtil is moved from org.activiti.impl.util.LogUtil to org.activiti.pvm.impl.util.LogUtil, however the logging.properties in the activiti-engine-init still references the old name.

Apparently, my windows box I'm currently working on, doesn't seem to mind about that and shows no exception when starting tomcat/deploying activiti-engine-init.

Show
Frederik Heremans added a comment - Stacktrace told me something is wrong with the Formatter used on the Filehandler: apache-tomcat-6.0.26-src -> org.apache.juli.FileHandler, line 333: writer.write(getFormatter().getHead(this)); The activiti-engine-init uses a custom Formatter, an inner class of LogUtil, LogUtil$LogFormatter. Since beta1, the PVM is separated into another module and LogUtil is moved from org.activiti.impl.util.LogUtil to org.activiti.pvm.impl.util.LogUtil, however the logging.properties in the activiti-engine-init still references the old name. Apparently, my windows box I'm currently working on, doesn't seem to mind about that and shows no exception when starting tomcat/deploying activiti-engine-init.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: