Has anyone any experience with this?
I have a small web service set up as a demo that works just fine under HTTP,
but when I attempt to connect via HTTPS, it craps out after the 3rd hit and
continuously returns the following exception until Tomcat is rebooted:
java.rmi.RemoteException
With the following message associated with it:
(0)null
(HTTP continues to work without problems. Even after HTTPS gives up the
ghost!)
catalina.out shows the following for every HTTPS hit once the 1st error
occurs:
Nov 7, 2003 3:27:55 PM
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler
processConnection
SEVERE: Error reading request, ignored
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Jdk14Logger does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja
va:532)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
va:272)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
va:246)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
at
org.apache.tomcat.util.net.jsse.JSSESupport.<init>(JSSESupport.java:87)
at
org.apache.tomcat.util.net.jsse.JSSE14Support.<init>(JSSE14Support.java:99)
at
org.apache.tomcat.util.net.jsse.JSSE14Factory.getSSLSupport(JSSE14Factory.ja
va:84)
at
org.apache.tomcat.util.net.jsse.JSSEImplementation.getSSLSupport(JSSEImpleme
ntation.java:118)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:385)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:619)
at java.lang.Thread.run(Thread.java:568)
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Jdk14Logger does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryI
mpl.java:416)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja
va:525)
... 11 more
Caused by: org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Jdk14Logger does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryI
mpl.java:412)
... 12 more
Any suggestions? The following is the https section from my server.xml
file. It took digging through the 5.0 documentation also before I could
even get HTTPS to work for TC 4.1.27. Seems IMB's JVM for JDK 1.4 has a few
twists to it that aren't documented until TC 5.0. And I'm real leery about
upgrading to a beta release (TC 5.0) unless I have to.
<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8023" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="100" debug="0" scheme="https" secure="true"
useURIValidationHack="false" disableUploadTimeout="true">
<Factory
className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory"
algorithm="IbmX509"
clientAuth="false" protocol="SSL" />
</Connector>
The server code being called. As you can see I just added outMsg & the
return value to the PortImpl.java stub that the axis WSDL2Java generated.
public java.lang.String testInterface(java.lang.String string)
throws java.rmi.RemoteException
{
String outMsg = System.getProperty ("java.vm.name") + " JDK " +
System.getProperty ("java.vm.version") +
" - " + System.getProperty ("user.name") +
" (" + string + ")";
return outMsg;
}
Curtis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
