title: Weblogic javax.net.ssl.SSLKeyException from node manager
body: <p>We have the following error shown in the node manager console.</p>
  
  <pre><code>&lt;Warning&gt; &lt;Uncaught exception in server handler: 
   javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was r
  eceived from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it 
  rejected the certificate chain (trusted CA configuration, hostname 
  verification). SSL debug tracing may be required to determine the exact 
  reason the certificate was rejected.&gt;
   javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was 
   received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it 
   rejected the certificate chain (trusted CA configuration, hostname 
   verification). SSL debug tracing may be required to determine the exact 
   reason the certificate was rejected. at
   com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown 
   Source)
  </code></pre>
  
  <p>Here are some details on the environment:
  Weblogic 10.  We are way past our support license.  However, things seem to work with no issues. Except we started getting this recently.</p>
  
  <p>Questions:
   - Can this be the cause of the following:</p>
  
  <pre><code>I can't restart any instance server from the web console app.  Only via some 
  command line scripts we are having here.
  </code></pre>
  
  <p>Also, can it be the cause of the following:</p>
  
  <pre><code>When I specify system property in 'Server Start' arguments, when I read it 
  with 'String sBaseOutputPath = System.getProperty("property.name");' it 
  returns null.
  </code></pre>
  
  <p>This problem (that exception trace mentioned above) occurs everywhere, on all our weblogic installations.  Dev, QA, production
  and the issues I presented, started recently, and the support license has expired a long-long time ago .. maybe 3 years ago.  This timing confuses me.  It suggest that there must be a way to around the problem.
  We are moving to another middle-ware, but while we are redesigning the systems, those running must be kept in shape.</p>
  
  <p><strong>Can anyone advise on what happens and if there is a way to go around it.</strong>  The major fear is that if for any reason we restart the production machine, we will not be able to start up weblogic services AT ALL !!</p>
  
  <p>Please, help !!  </p>