URLConnection and Weblogic 6.1 Problem

Question

I am trying to create a URL connection to a secure site from within a JSP. This is the code I am using
  try {
    System.setProperty("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
    URL url = new URL("https://secure2.mde.epdq.co.uk/cgi-bin/CcxBarclaysEpdqEncTool.e");
    URLConnection conn = (URLConnection)url.openConnection();
    conn.setDoOutput(true);
    conn.setUseCaches(false);
    conn.setRequestProperty("content-type", "application/x-www-form-urlencoded");
    OutputStream outStream = conn.getOutputStream();
  } catch(IOException e) {
    e.printStackTrace();
  }The problem is that when conn.getOutputStream() is executed I receieve a fatal handshake error. I am running the JSP on weblogic 6.1 with JDK1.3. I have added the JSSE libs and made the necessary changes in java.security.
I can run the same code as a stand-alone application (using jdk1.3 still) with no problems. However once deployed to weblogic 6.1 it crashes. It does work on WL 8.1 (but this is not an option).
I have enabled ssl debugging within WL and receive the following
####<28-Nov-07 17:15:05 GMT> <Debug> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <Before license check - client CipherSuites: [3,9,8,0] server CipherSuites: [3,9,8,0]>
####<28-Nov-07 17:15:05 GMT> <Debug> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <No SSL/Domestic License found>
####<28-Nov-07 17:15:05 GMT> <Debug> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <After license check - client CipherSuites: [3,9,8,0] server CipherSuites: [3,9,8,0]>
####<28-Nov-07 17:15:05 GMT> <Info> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <V2 client hello sent: version = 3.0, cipherSpecs = 4 {3, 9, 8, 0}, sessionID = 0 , challenge = 32 474da2196582eaff9b46529ac4ee36f563c13815a67e92bb385d72226f66ed7d>
####<28-Nov-07 17:15:05 GMT> <Info> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <Decrypting 2 bytes...>
####<28-Nov-07 17:15:05 GMT> <Info> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> < Finished decrypting 2 bytes>
####<28-Nov-07 17:15:05 GMT> <Info> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> < Read throughput = Infinity bytes/sec>
####<28-Nov-07 17:15:05 GMT> <Info> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <contentLen = 2, padding.length = 0, MAC.length = 0, len = 2>
####<28-Nov-07 17:15:05 GMT> <Info> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <Available on alertStream: 2>
####<28-Nov-07 17:15:05 GMT> <Info> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <Aborting session>
####<28-Nov-07 17:15:05 GMT> <Info> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <Alert: fatal handshake_failure>
####<28-Nov-07 17:15:05 GMT> <Info> <SSL> <dt04230> <hwserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <Aborting session> I have not changed any of WL's keystores from the default settings but I would have thought it would use the standard java cacerts which is obviously fine as I ran the app stand-alone.
If any body has faced this issue or knows of a possible solution I would greatly appreciate any response.
Thanks

Answer 1

As you said, it could be the WLS6 truststore which doesn't contain the certificate authority. Just check which files are used (cacerts, cacerts.jks,..), and maybe you can find it by checking the option startup : -Dweblogic.security.SSL.trustedCAKeyStore
It doesn't matter when the exception is triggered (you can do an explicit handshake, or just write in the socket and then wait for an implicit handshake)