DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22701>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22701

commons-logging and SSL in tomcat with struts

           Summary: commons-logging and SSL in tomcat with struts
           Product: Struts
           Version: 1.1 Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Controller
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


I'm not sure what library is failing here. It could be either tomcat, struts or 
common-logging itself. Here is the problem. My application is running under 
tomcat (jakarta-tomcat-4.1.27-LE-jdk14) using struts (jakarta-struts-1.1). I'm 
using log4j as the logging implementation. I have the following jar files in 
the application's WEB-INF directory:

commons-beanutils.jar
commons-collections.jar
commons-digester.jar
commons-fileupload.jar
commons-lang.jar
commons-logging.jar
commons-validator.jar
jakarta-oro.jar
struts.jar

log4j-1.2.8.jar
rowset.jar

Everything works fine till I try to access my application through https:// 
protocol. I'm getting the following exception:

org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging
.LogConfigurationException: org.apache.commons.logging.LogConfigurationException
: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log
        at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:532)
        at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:272)
        at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:246)
        at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
        at org.apache.tomcat.util.net.jsse.JSSESupport.<init>(JSSESupport.java:8
7)
        at org.apache.tomcat.util.net.jsse.JSSE14Support.<init>(JSSE14Support.ja
va:99)
        at org.apache.tomcat.util.net.jsse.JSSE14Factory.getSSLSupport(JSSE14Fac
tory.java:84)
        at org.apache.tomcat.util.net.jsse.JSSEImplementation.getSSLSupport(JSSE
Implementation.java:118)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:385)
        at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:565)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:619)
        at java.lang.Thread.run(Thread.java:534)
Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.comm
ons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Log
4JLogger does not implement Log
        at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:416)
        at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:525)
        ... 11 more
Caused by: org.apache.commons.logging.LogConfigurationException: Class org.apach
e.commons.logging.impl.Log4JLogger does not implement Log
        at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogF
actoryImpl.java:412)
        ... 12 more

If I remove the commons-logging.jar from WEB-INF/lib then everything works 
fine. However, no logging is performed in struts actions.

I've seen some postings suggested that only one commons-logging.jar should be 
in the classpath. I know that tomcat has it's own server/lib/commons-
logging.jar that is identical (based on the manifest file) to the one that came 
with struts. In any case, I've tried to copy server/lib/commons-logging.jar 
into WEB-INF/lib - same result - an exception when https:// is used.

The only solution that I have is to use log4j directly in actions (as I do in 
BO, DAO layers anyway)

Any ideas ?
Thanks
Pavel

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to