Thursday, February 18, 2016

Funny error message using t3s and 2 way SSL

javax.naming.CommunicationException: t3s://localhost:25001: Destination 0:0:0:0:0:0:0:1, 25001 unreachable; nested exception is: Received fatal alert: bad_certificate; No available router to destination 

but there was absolutely no issue with the localhost or the port or anything else... WebLogic was listening on all IPv4 and IPv6 addresses on 25001...
googling around I find:

If the Client keystore/truststore PATH is not valid, so check the path specified in “” (OR) if the client keystore does not include the WebLogic certificate imported in it then we may see the following kind of error: Destination 0:0:0:0:0:0:0:1, 7443 unreachable.; nested exception is: Received fatal alert: handshake_failure; [RJVM:000576]No available router to destination.; nested exception is: 
    java.rmi.ConnectException: [RJVM:000576]No available router to destination.

check that what you are using as trust store and identity store are valid, and that valid password and alias is provided....

No comments: