Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

javax.net.ssl.SSLException: untrusted server cert chain

 
Ron Summer
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
I hope I can get some help with the above error. The background is I have two different URL's connections( A and B) in my application. They both call a different secured server requesting data. The error below is always returned when the second request is being made. If I run request A first the request completes fine. But when I run the B request the error occurs. The flip side is when I shut the application down and re-run with the B request first the request completes fine, but the A request produces the error. Both A and B sessions are on their own Thread that terminates after breaking the requested file into usable parts.

I'm not sure if it's relevant or not but in the (A)(B)Connection properties sslSocketFactory has an array of http: sites that has been requested. It continues to grow with each new request and it does not matter which class I look at the Connection properites. I am wondering it their is a way to reset that array or move items form the list? At this point I'm not even sure if it's relevant.

Thanks for any and all help.

The stack trace it produces is as:

javax.net.ssl.SSLException: untrusted server cert chain
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(DashoA12275)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(DashoA12275)
at java.io.OutputStream.write(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(DashoA12275)
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.doConnect(DashoA12275)
at com.sun.net.ssl.internal.www.protocol.https.NetworkClient.openServer(DashoA12275)
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.l(DashoA12275)
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.<init>(DashoA12275)
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.<init>(DashoA12275)
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a(DashoA12275)
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a(DashoA12275)
at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(DashoA12275)
at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.getOutputStream(DashoA12275)


 
Satya Maheshwari
Ranch Hand
Posts: 368
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Though may not be related, any particular reason you explicitly adding a provider and using the default one.
 
Ron Summer
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

If I don't add the com.sun.net.ssl.internal.ssl.Provider provider I get an error of no SSL implementation.

Any other suggestions comments? This one has really got me puzzled.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic