Activiti

Move logging.properties process activiti-engines-init to tomcat installation

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 5.0.beta2
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

curerntly the logging.properties is in the activiti-engines-init webapp.
copying of that file into the right place should be moved to the setup tool in the target to install activiti into tomcat. it should only be done when tomcat is the server.

Issue Links

This issue depends upon:
ACT-127 Restructure modules Major Resolved

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tom Baeyens added a comment -

source file should be moved from the activiti-engines-init webapp to the setup files

Show
Tom Baeyens added a comment - source file should be moved from the activiti-engines-init webapp to the setup files
Hide
Permalink
Frederik Heremans added a comment -

Also include the default handlers (catalina, localhost etc) in the logging.properties toghether with the custom activiti-handler.

Show
Frederik Heremans added a comment - Also include the default handlers (catalina, localhost etc) in the logging.properties toghether with the custom activiti-handler.
Hide
Permalink
Frederik Heremans added a comment -

When I move the activiti FileHandler definition (with a custom formatter) to the global tomcat logging-config, I get a similar error as in issue ACT-94, so I presume the formatter cannot be instantiated.

When tomcat bootstraps, it initialises it's global logging, but I suspect this is done in the "System" (http://spdn.ifas.ufl.edu/docs/class-loader-howto.html) classloader, before the core engine is started. The problem is that the System class-loader only contains 2 jars: bootstrap and tomcat-juli (logging) and none of the libs in '$tomcat-home/lib/' are included, which offcourse contains the formatter we configured (org.activiti.pvm.impl.util.LogUtil$LogFormatter)

Show
Frederik Heremans added a comment - When I move the activiti FileHandler definition (with a custom formatter) to the global tomcat logging-config, I get a similar error as in issue ACT-94, so I presume the formatter cannot be instantiated. When tomcat bootstraps, it initialises it's global logging, but I suspect this is done in the "System" (http://spdn.ifas.ufl.edu/docs/class-loader-howto.html) classloader, before the core engine is started. The problem is that the System class-loader only contains 2 jars: bootstrap and tomcat-juli (logging) and none of the libs in '$tomcat-home/lib/' are included, which offcourse contains the formatter we configured (org.activiti.pvm.impl.util.LogUtil$LogFormatter)
Hide
Permalink
Frederik Heremans added a comment -

As an alternative, we will use the default tomcat-logging without a custom Formatter and add entry for org.activiti.* classes log level.

Show
Frederik Heremans added a comment - As an alternative, we will use the default tomcat-logging without a custom Formatter and add entry for org.activiti.* classes log level.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.