Perhaps it's related to the Verisign intermediate signing
certificate which expired last week.  Check the Verisign website
for details.

Alex

>>>>> "Neal" == Neal  <[EMAIL PROTECTED]> writes:
  Neal> To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
  Neal> Subject: javax.net.ssl.SSLHandshakeException: Could not find trusted
  Neal>          certificate
  Neal> Date: Mon, 12 Jan 2004 23:05:41 -0800

  Neal> I suddenly have a problem reading XML over SSL, where the system has
  Neal> been in place for a year and the problem never existed before! And the
  Neal> weird part is that both my dev and production environmets now seem to
  Neal> have the same problem.

  Neal> Another interesting tidbit I have noticed is that I *can* access XML
  Neal> documents on my own server (using a Thawte cert) but have a problem
  Neal> when attempting to access documents on two external servers that I know
  Neal> use Verisign certs.  This may or may not be related.

  Neal> Can anyone think of what may be wrong or what I can do to correct the
  Neal> issue?


  Neal> I am getting the following error: javax.net.ssl.SSLHandshakeException:
  Neal> Could not find trusted certificate


  Neal> Here is the method I am using to retrieve the document: public Document
  Neal> readDocument(URL url) throws IOException, ParserConfigurationException,
  Neal> SAXException {
  Neal>         Document doc = null;
  Neal>       InputStream in = url.openStream(); DocumentBuilderFactory
  Neal>       docBuilderFactory =
  Neal> DocumentBuilderFactory.newInstance();
  Neal>       DocumentBuilder docBuilder =
  Neal> docBuilderFactory.newDocumentBuilder();
  Neal>       doc = docBuilder.parse(in); return doc;
  Neal>     }






-- 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to