Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
uninitialized keystore error with SSL connection
I wish I could award 1,000,000 points to anyone that can help me figure out an intermittent problem. We have a system interface to an external company's server. The connection uses SSL. We have a key in our keystore and a certificate from the company. In some cases the interface works fine. In other cases we get a handshake failure. The error message is "Uninitialized keystore." The code is written in Java. We are using Java 1.6. I have SSL debug output where I can see the handshake failure. But I don't know enough to understand why we are getting the handshake failure. Can you help me track down the source of this intermittent problem?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
We have a system interface to an external company's server.It's conceivable they are the source of the error, and that it doesn't reside in your code
They have many, many customers accessing their system and they say that we are the only one running into this error. The strange thing is that sometimes it works and sometimes it does not work. The problem seems to be on our side.
Might be worthwhile posting an obfuscated ssl debug log
Have you tried a different runtime?
Does it happen on different boxes on your side or just one?
Have you tried a different runtime?
Does it happen on different boxes on your side or just one?
Sure an ssl debug log would definitely help.
Hard to help without this.
It would also help to know which kind of cases work and which do not.
Also you could use this class to test your SSL connection.
Using it with your keystore to access your secured server would show you if the SSL connection is ok or not. And it would show you the certificate sent by the server.
Here is the class : http://code.google.com/p/java-use-examples/source/browse/trunk/src/com/aw/ad/util/InstallCert.java
May be you could try it and show us the result.
Another thing i'm wondering.
Do you configure your keystore in the code and actually load it? Something like :
keyStore.load(...) ?
Is there a line of code before the load call that could raise an exception, causing the load method not being executed ?
Hard to help without this.
It would also help to know which kind of cases work and which do not.
Also you could use this class to test your SSL connection.
Using it with your keystore to access your secured server would show you if the SSL connection is ok or not. And it would show you the certificate sent by the server.
Here is the class : http://code.google.com/p/java-use-examples/source/browse/trunk/src/com/aw/ad/util/InstallCert.java
May be you could try it and show us the result.
Another thing i'm wondering.
Do you configure your keystore in the code and actually load it? Something like :
keyStore.load(...) ?
Is there a line of code before the load call that could raise an exception, causing the load method not being executed ?
Are you getting this problem in some particular scenario?
I use to get Handshake problem while using Https url's, but I think this is not the case with you.
If you are using Distributed system then there might be the chance that it is failing for one particular server.
If the same certificate is used by other application on the same server, then there might be chances that it is getting initialized because of other application.
Are you facing this problem after restarting the application/server or it is coming intermittently without restarting it.
I use to get Handshake problem while using Https url's, but I think this is not the case with you.
If you are using Distributed system then there might be the chance that it is failing for one particular server.
If the same certificate is used by other application on the same server, then there might be chances that it is getting initialized because of other application.
Are you facing this problem after restarting the application/server or it is coming intermittently without restarting it.
This is still an issue. Is it possible that using the Url class is overwriting the values of the java.ssl session variables? Our code is using the session variables to set the keystore and certificate file names. Is there another class that would overwrite these session variable values?
Possibly tomcat may have an environment setting specifying a keystore, but if a class inside the code overrides it, the latest should be used.
One good way to see if your keystore is used is to turn on ssl debug. Add -Djavax.net.debug=all to your launch config. Then when your app is launched, you should see a lot of things related to ssl in the log. One thing is the loaded keystore, and all the certificates and keys it contains. If your keystore contains a few certificates, you should see them. If, instead, you have a lot of certificates listed in the log, chances are that your keystore is not loaded, and that instead, the jdk default one is used.
Furthermore, with this debug enabled, you'll see the ssl debug log when your problem appears. It will show the certificates compared to the one you receive from server, and an error message if no matching certificate is found.
Once again, if possible, an ssl debug log would definitely help us to diagnose (at least try :) ) your problem. Oh and of course, the ssl debug log of a succesful connection would also help. Comparing these fail/success debugs would give a hint i guess.
One good way to see if your keystore is used is to turn on ssl debug. Add -Djavax.net.debug=all to your launch config. Then when your app is launched, you should see a lot of things related to ssl in the log. One thing is the loaded keystore, and all the certificates and keys it contains. If your keystore contains a few certificates, you should see them. If, instead, you have a lot of certificates listed in the log, chances are that your keystore is not loaded, and that instead, the jdk default one is used.
Furthermore, with this debug enabled, you'll see the ssl debug log when your problem appears. It will show the certificates compared to the one you receive from server, and an error message if no matching certificate is found.
Once again, if possible, an ssl debug log would definitely help us to diagnose (at least try :) ) your problem. Oh and of course, the ssl debug log of a succesful connection would also help. Comparing these fail/success debugs would give a hint i guess.
Is there a way to send you the ssl debug log privately? I am very reluctant to post the log file to the public as this file belongs to my client.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial