After synching up the 2 systems a bit more, I am getting a FileNotFound message (not sure if this is a step back or a step forward):
java.io.FileNotFoundException: https://server2:443/servlet/ContactServlet?target=server1 at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.<init>(Throwable.java:94) at java.lang.Exception.<init>(Exception.java:42); at java.io.IOException.<init>(IOException.java:47); at java.io.FileNotFoundException.<init>(FileNotFoundException.java:53); at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.getInputStrea m([DashoPro-V1.2-120198]); But, the URL is legal (responds from the browser and the command line). Is anyone doing SSL out from Tomcat to another Apache/Tomcat? Any ideas of what to try next? Mitchell Evan Marx [EMAIL PROTECTED] AT&T IP Network Configuration & Provisioning Development -----Original Message----- From: Marx, Mitchell E (Mitch), ALSVC Sent: Wednesday, November 28, 2001 4:38 PM To: Tomcat Users List Subject: server to server https communication Configuration: Solaris 2.6, Apache 1.3.20, Tomcat 3.2.3, mod_ssl, mod_jk 3.3, java 1.2 Server 1 - Apache running SSL (A) Tomcat server running client ----> (B) Server 2 - Apache running SSL Tomcat server running servlet When (A) opens an SSL connection to (B) I get: javax.net.ssl.SSLException: untrusted server cert chain at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.<init>(Throwable.java:94) at java.lang.Exception.<init>(Exception.java:42) at java.io.IOException.<init>(IOException.java:47) at javax.net.ssl.SSLException.<init>([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.ssl.ClientHandshaker.a([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage([DashoPro-V1.2- 120198]) at com.sun.net.ssl.internal.ssl.Handshaker.process_record([DashoPro-V1.2-120198 ]) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a([DashoPro-V1.2-120198]) at com.sun.net.ssl.internal.ssl.AppOutputStream.write([DashoPro-V1.2-120198]) at java.io.OutputStream.write(OutputStream.java:65) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake([DashoPro-V1.2-120 198]) at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.doConnect([DashoPro- V1.2-120198]) at com.sun.net.ssl.internal.www.protocol.https.NetworkClient.openServer([DashoP ro-V1.2-120198]) at com.sun.net.ssl.internal.www.protocol.https.HttpClient.l([DashoPro-V1.2-1201 98]) at com.sun.net.ssl.internal.www.protocol.https.HttpClient.<init>([DashoPro-V1.2 -120198]) at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.<init>([DashoPro-V1. 2-120198]) at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V1.2-120 198]) at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V1.2-120 198]) at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect([Dash oPro-V1.2-120198]) at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.getInputStrea m([DashoPro-V1.2-120198]) It is able to create the URL and open the connection. Command line (C) Java program running same code ---> (B) (same as above) works fine?!? In both cases, I make sure the call to java contains the following: -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol -Djavax.net.ssl.trustStore=/usr/local/tomcat/ca.crt The ca.crt file is created via the java 1.2 keytool: ${JAVA_HOME}/jre/bin/keytool -import -alias tomcat -file server.crt -keystore ca.crt server.crt generated by openssl OR Verisign trial cert. Same problem with either. Any ideas? Mitchell Evan Marx [EMAIL PROTECTED] AT&T IP Network Configuration & Provisioning Development -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
