Sounds like an issue with the algorithms supported by your certificate and those supported by your SSL implementation.
For example, if your certificate has an RSA public key and you don't have an RSA implementation then you would probably get something like this. Or it may be due to the supported key lengths, e.g. 512 vs 1024 bits or whatever.
I would check out the differences between your self-generated certificate and the Thawte one, and try generating your own certificates with similar info to the Thawte one and see if these work. You can also use OpenSSL to do this sort of thing (but it's not trivial :).
Thanks Luke, I'll try your suggestion.
I guess mainly I was just looking for someone to give me a "thumbs up" that they have successfully used a Thawte, or Verisign, cert with JBoss/Tomcat.
I succeed with the Verisign trial cert...
I imported the trial cert into the keystore file.
I used the same alias with my key...
The trial cert is attached my key entry and cert chain lengths are increased to 2.
When I typeed https, I got the page with the trial cert...
Can you please explain the steps you did to make this work?