Issue2641

With JAVA 8.1 and jython-standalone-2.7.1.jar , 

observed following error :-
certificate verify failed (javax.net.ssl.SSLHandshakeException: General SSLEngine problem)


refer this old issue for more details:-
http://bugs.jython.org/issue2614,

I want to know what could be the problem here.

Is there some method to generate some debug logs for this issue.

Any updates on this. ? this issue is critical.

There is some discussion about a similar problem also where Netty is being used here https://github.com/lightbody/browsermob-proxy/issues/615

I don't think we can really investigate this at the moment can you provide some example code which demonstrates this is a Jython problem? The smaller the better. The current information doesn't suggest anything is going wrong in Jython.

My initial guess is this is a security configuration issue with the certificates or the JVM but its not an area im expert in.

I dont think it is security configuration issue with the certificates or JVM in our system. We are not making any changes in configurations related to security while using this jar. I also mentioned in my old bug that old jython jar 2.7.0 does not create this problem but this new jar does. 
There are some changes in the new jar 2.7.1 which is causing issue. Our code remains the same whatever part it is. 


please see the below code which shows the problem:-

[root@sccm2106 bin]# ./sccmCLI.sh 
certificate verify failed (javax.net.ssl.SSLHandshakeException: General SSLEngine problem) (1)
[root@sccm2106 bin]# 


sccmClI.sh

. `dirname $0`/setupEnv.sh
$JAVA_CMD -jar $TUAM_LIB/jython-standalone-2.7.1.jar $TUAM_BIN/sccmCLI.py "$@"



Thanks, 
Neha

Hi Neha: one would need to know what was in sccmCLI.py and what the environment was, to have any chance of progress. However, that could be complicated.

A simple sequence of operations that really ought to work and doesn't is what we need to understand what bug you have discovered for us.

The message *ought* to mean that the certificate presented by the service you are connecting to is not trusted by the JVM. Just enough code to open the connection would  prove the config is good. Then add code until you prove the Jython libraries as used are mis-handling certificates, connections, etc..