title: Weblogic servers SSL issue on HTTPS
body: <p>I'm using weblogic 10.3.6 and I've deployed application A and B into the same box but different server instance.</p>
  
  <p>Both servers are choosing 'Client Certs Not Requested' for the two way client cert behavior in SSL configurations.</p>
  
  <p>Everytime we restart the servers, it was working fine on the same day. However from the next day onward, I am getting the following error when application A try to invoke a https server request to application B. </p>
  
  <p>Weblogic server log trace:</p>
  
  <pre><code>    &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;Filtering JSSE SSLSocket&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;SSLIOContextTable.addContext(ctx): 455813&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;SSLSocket will  be Muxing&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;isMuxerActivated: false&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;20666515 SSL Version 2 with no padding&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;21699288 SSL3/TLS MAC&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;21699288 received SSL_20_RECORD&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;HANDSHAKEMESSAGE: ClientHelloV2&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;write HANDSHAKE, offset = 0, length = 58&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;write HANDSHAKE, offset = 0, length = 4809&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;write HANDSHAKE, offset = 0, length = 4&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;isMuxerActivated: false&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;21699288 SSL3/TLS MAC&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;21699288 received ALERT&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;NEW ALERT with Severity: FATAL, Type: 46
      java.lang.Exception: New alert stack
          at com.certicom.tls.record.alert.Alert.&lt;init&gt;(Unknown Source)
          at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
          at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
          at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
          at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
          at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
          at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
          at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
          at javax.net.ssl.impl.SSLSocketImpl.startHandshake(Unknown Source)
          at weblogic.server.channels.DynamicSSLListenThread$1.run(DynamicSSLListenThread.java:130)
          at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
          at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
      &gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;Alert received from peer, notifying peer we received it: com.certicom.tls.record.alert.Alert@925980&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Warning&gt; &lt;Security&gt; &lt;BEA-090485&gt; &lt;CERTIFICATE_UNKNOWN alert was received from serverB- 192.168.1.XXX. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;close(): 20666515&gt; 
      &lt;Apr 15, 2014 10:32:34 AM SGT&gt; &lt;Debug&gt; &lt;SecuritySSL&gt; &lt;BEA-000000&gt; &lt;close(): 20666515&gt; 
  </code></pre>