Sukhwinder,
I've faced this problem before. It's got something to do with where your
JAR's are placed in the classpath.
If the class throwing this exception is somewhere inside tomcat's internal
classes (webserver.jar) then move it to a place other than the default /lib
folder and inclde it in the class path.
I'm not sure if that answered your question but try it out and also search
on the net for "Sealing violation". I digged it out of the archives and the
reply from Craig was a solution similar to this which worked for me
Anand
At 02:14 PM 9/5/01 -0700, you wrote:
>Hello,
>
> This is the third time I am sending email. No one is replying.
>
> I have downloaded tomcat version 3.2.3 source code and compiled it on my
>windows 95 machine with Sun JDk 1.3.1. I also had to download JSSE because
>there was no option to compile without ssl support. If these classes are not
>in classpath then source doesn't compile. My problem is when after compiling
>distribution when I try to start tomcat following errors is produced:
>
>///////////////////////////////
>FATAL Configuration error:
>java.lang.SecurityException: sealing violation
>..........
>..........
>////////////////////////////////////
>
>I have followed that steps provided in SSL howto about making entry in java
>security file and using keytool.
>For password it is written that password can be "changeit" but when keytool
>asks about alias tomcat password what should be entered. (i.e. what is the
>tomcat admin password).
>
>Please help me in solving above problem because I am unable to start tomcat.
>
>Is there any option to compile tomcat without ssl support?
>
>Sukhwinder Singh
>
>
>
>
>
>_______________________________________________________
>Send a cool gift with your E-Card
>http://www.bluemountain.com/giftcenter/
