Re: No one answering my question (security realted problem)

2001-09-07 Thread Sukhwinder Singh

>  Completely clear your CLASSPATH. Then, install a fresh copy of >Tomcat.
Then,
  >try to access some of the sample servlets.
  
  >If that doesn't work, you might want to give Tomcat 4 a try. >Tomcat 4 is
due out in mid-September. Tomcat 4 doesn't use CLASSPATH at all, so, maybe
that'll fix your problem.
  
>Also, make sure you're running the latest version of Sun's JDK, 1.3.1.
  
  Jon
  
Yes I am using jdk1.3.1. I had already cleared the classpath which was set
using autoexce.bat when I found in mail archive that two servlet.jar in
classpath can cause this sealing violation . My problem is only related to
tomcat 3.2.3 and version 3.2.2 works well.

Sukhwinder Singh

  - Original Message -
  From: "Sukhwinder Singh" <[EMAIL PROTECTED]>
  To: <[EMAIL PROTECTED]>
  Sent: Thursday, September 06, 2001 4:10 PM
  Subject: Re: No one answering my question (security realted problem)
  
  
  >
  >   >It's unclear to me why you're recompiling tomcat.  Why not just >use
a
  > binary
  >   >distribution?  I've never compiled it from source...
  >
  >   >dwh
  >
  > Hello,
  >   I have also downloaded binary version of tomcat 3.2.3 but even that
  > doesn't start.
  >
  > SS
  >
  >
  >
  >
  >
  > ___
  > http://inbox.excite.com
  >
  >
  





___
http://inbox.excite.com





Re: No one answering my question (security realted problem)

2001-09-06 Thread Jonathan Eric Miller

Completely clear your CLASSPATH. Then, install a fresh copy of Tomcat. Then,
try to access some of the sample servlets.

If that doesn't work, you might want to give Tomcat 4 a try. Tomcat 4 is due
out in mid-September. Tomcat 4 doesn't use CLASSPATH at all, so, maybe
that'll fix your problem.

Also, make sure you're running the latest version of Sun's JDK, 1.3.1.

Jon

- Original Message -
From: "Sukhwinder Singh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 06, 2001 4:10 PM
Subject: Re: No one answering my question (security realted problem)


>
>   >It's unclear to me why you're recompiling tomcat.  Why not just >use a
> binary
>   >distribution?  I've never compiled it from source...
>
>   >dwh
>
> Hello,
>   I have also downloaded binary version of tomcat 3.2.3 but even that
> doesn't start.
>
> SS
>
>
>
>
>
> ___
> http://inbox.excite.com
>
>




Re: No one answering my question (security realted problem)

2001-09-06 Thread Sukhwinder Singh


  >It's unclear to me why you're recompiling tomcat.  Why not just >use a
binary
  >distribution?  I've never compiled it from source...
  
  >dwh
  
Hello,
  I have also downloaded binary version of tomcat 3.2.3 but even that
doesn't start.

SS





___
http://inbox.excite.com





Re: No one answering my question (security realted problem)

2001-09-06 Thread Anand B N

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/





Re: No one answering my question (security realted problem)

2001-09-05 Thread Denis Haskin

Sukhwinder Singh wrote:

> Hello,
>
>  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.  ...
> Is there any option to compile tomcat without ssl support?

It's unclear to me why you're recompiling tomcat.  Why not just use a binary
distribution?  I've never compiled it from source...

dwh




Re: No one answering my question (security realted problem)

2001-09-05 Thread Dmitri Colebatch

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/
> 
> 
> 




No one answering my question (security realted problem)

2001-09-05 Thread Sukhwinder Singh

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/