Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I configured tomcat with SSL successfully and was using a self-signed certificate. Recently an issue arose where just having the client "Accept/trust" our certificate wasn't easy. We ended up purchasing a verisigin certificate for that server.

I've added the new certificate to the certificate to the key store. I've updated tomcat's server.xml file to use the alias, for the new certificate. I've restarted both Tomcat and the Server. Everytime I connect to the server I get the old Certificate.


  • Windows 2008 R2 - 64bit
  • Tomcat 6.0.29 - installed as a service
  • Java 1.6.0_23

Connector from server.xml:

<Connector port="443" maxThreads="150" 
           scheme="https" secure="true" SSLEnabled="true"
           keystoreFile="keystore.keys" keyalias="webapps2013"
           clientAuth="false" sslProtocol="TLS" protocol="HTTP/1.1" />

I've even tried changing the key store, by moving the old certificate to a different alias and adding my new certicate at what the old alias name was.

I've tried it from multiple browsers, and workstations. (Cleared my cache too.)

So what do I need to do to get tomcat to pickup and serve my new certificate?

After a suggestion in one of the comments to clear tomcats cache.
I stopped tomcat, deleted ${CATALINA_HOME}/work and restarted tomcat.
It's still serving the old certificate.

I've looked through *jakarta_service_date.log* ** and I don't see any certificate errors. Although I am Seeing an odd error about Session Serialization.

Dec 11, 2013 10:46:27 AM org.apache.catalina.session.StandardManager doUnload
SEVERE: IOException while saving persisted sessions: 
C:\Tomcat6.0\work\Catalina\localhost\RCSLIBRRunner\SESSIONS.ser (Access is denied) C:\Tomcat6.0\work\Catalina\localhost\RCSLIBRRunner\SESSIONS.ser (Access is denied)

followed by a stacktrace. Other Applications threw tha similar same exception. It hasn't happened in a couple hours, I think it was a side effect from clearing tomcats cache.

Here's another Serialization error:

Dec 11, 2013 10:46:27 AM org.apache.catalina.session.StandardManager stop
SEVERE: Exception unloading sessions to persistent storage C:\Tomcat6.0\work\Catalina\localhost\RCSLIBRRunner\SESSIONS.ser (Access is denied)
share|improve this question
Did you try to clear the Tomcat cache files ? – krisFR Dec 11 '13 at 19:18
Which files are those? – Raystorm Dec 11 '13 at 19:42
Stop Tomcat service, then delete the folder named "Catalina" in your "work" folder, and restart Tomcat service – krisFR Dec 11 '13 at 19:54

We had trouble with the protocol="HTTP/1.1", with errors in our logs. Our errors were

Certificate file specified or invalid file format

Based on some "google research", we used this for protocol instead:


Our Connector is as follows:

<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
    sslProtocol="TLS" />
share|improve this answer

turns out I had a typo in my Connector

It should be:

<Connector port="443" maxThreads="150" 
           scheme="https" secure="true" SSLEnabled="true"
           keystoreFile="keystore.keys" keyAlias="webapps2013"
           clientAuth="false" sslProtocol="TLS" protocol="HTTP/1.1" />

Note: the first a in keyAlias is capitalized.

Turns out that if the alias isn't listed it just silently serves the first key it finds in the key store.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.