[jopr-issues] [JBoss JIRA] Updated: (JOPR-101) response time filter fails when dropped into standalone Tomcat 6

[Jay Shaughnessy (JIRA)]

     [ https://jira.jboss.org/jira/browse/JOPR-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Shaughnessy updated JOPR-101:
---------------------------------

    Component/s: Plugin - Tomcat


> response time filter fails when dropped into standalone Tomcat 6
> ----------------------------------------------------------------
>
>                 Key: JOPR-101
>                 URL: https://jira.jboss.org/jira/browse/JOPR-101
>             Project: Jopr
>          Issue Type: Bug
>          Components: Plugin - Tomcat
>    Affects Versions: 2.2
>         Environment: Tomcat6, EWS Tomcat6
>            Reporter: Jay Shaughnessy
>            Priority: Critical
>             Fix For: 2.2
>
>
> Tomcat6 restructured their logging approach for a smaller footprint and, I think, less configuration collisions for commons logging/log4j.  The response time filter assumes availability of commons logging in the classpath.  This is no longer there by default in TC6 so the rtfilter immediately fails with class not found issues.
> The simplest solution may be to include a commons logging jar in the connector-rtfilter.zip and let the unzip deliver both the filter and logging jar.   It would have to be compatible with the various versions of Tomcat.  Or, we could document the instructions for getting the common logging jar for TC6.
> Dropping the version of commons-logging packaged in EWS TC5 seems to work for EWS TC6.
> Opinions?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira