There have been several mails recently about the sealing violation on user
and dev - it might be worth doing a check of the archives.
however, if you dont require ssl (which by the sounds of it you dont),
then the quickest solution for you is likely to be downloading a binary
instead of the source... any reason why that wouldn't fulfil your needs?
cheers
dim
On Wed, 5 Sep 2001, Sukhwinder Singh 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/
>
>
>
