Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 1060534, 1 year ago
[Security:090482]BAD_CERTIFICATE alert was received from botd.devop.com - 192.12.12.13. 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.
via Oracle Community by user11062519, 1 year ago
[Security:090482]BAD_CERTIFICATE alert was received from tabssb09 - 10.50.7.176. 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.
via Oracle Community by 673103, 1 year ago
[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.
via middlewaremagic.com by Unknown author, 1 year ago
[Security:090482]BAD_CERTIFICATE alert was received from hwvalad2021 – 172.21.80.118. 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.
via hivmr.com by Unknown author, 2 years ago
[Security:090482]BAD_CERTIFICATE alert was received from ics027dor - 10.184.134.109. 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.
via Oracle Community by 784017, 1 year ago
[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.
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from botd.devop.com - 192.12.12.13. 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)	at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)	at com.certicom.tls.record.alert.AlertHandler.handle(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 com.certicom.tls.record.ReadHandler.read(Unknown Source)	at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)	at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)	at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)	at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)	at java.io.InputStreamReader.read(InputStreamReader.java:167)	at java.io.BufferedReader.fill(BufferedReader.java:136)	at java.io.BufferedReader.readLine(BufferedReader.java:299)	at java.io.BufferedReader.readLine(BufferedReader.java:362)	at weblogic.nodemanager.server.Handler.run(Handler.java:71)	at java.lang.Thread.run(Thread.java:662)