You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Terrence Martin <tw...@its.to> on 2001/10/15 20:05:30 UTC
Problems loading server.xm lin Tomcat 4.0.1
I get the following error when I try to run tomcat 4.0.1. The error shows
up in catalina.out.
Basically it looks like tomcat cannot find its config file. However ls
seems to find it fine. Anyone else have this problem? I will note that I
have made no changes to tomcat, just untar'd it and tried to run it.
Tomcats error
PARSE error at line 0 column 0 of
/home/local/tomcat-4.0.1/bin/./../conf/server.xml
org.xml.sax.SAXParseException: File
"file:/home/local/tomcat-4.0.1/bin/./../conf/server.xml" not found.
Catalina.start: org.xml.sax.SAXParseException: File
"file:/home/local/tomcat-4.0.1/bin/./../conf/server.xml" not found.
org.xml.sax.SAXParseException: File
"file:/home/local/tomcat-4.0.1/bin/./../conf/server.xml" not found.
at java.lang.Throwable.<init>(Throwable.java:96)
at java.lang.Exception.<init>(Exception.java:44)
at org.xml.sax.SAXException.<init>(SAXException.java:45)
at org.xml.sax.SAXParseException.<init>(SAXParseException.java:56)
at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1202)
at
org.apache.xerces.readers.DefaultEntityHandler.startReadingFromDocument(DefaultEntityHandler.java:512)
at
org.apache.xerces.framework.XMLParser.parseSomeSetup(XMLParser.java:312)
at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1080)
at
org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.java:223)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:290)
at
org.apache.catalina.util.xml.XmlMapper.readXml(XmlMapper.java:228)
at org.apache.catalina.startup.Catalina.start(Catalina.java:725)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
My own ls
user@host ~$ ls -l /home/local/tomcat-4.0.1/bin/./../conf/server.xml
-rw-r--r-- 1 root root 15743 Oct 14 12:15
/home/local/tomcat-4.0.1/bin/./../conf/server.xml
Cheers,
Terrence
Re: 4.0.1 just cores
Posted by Fredrik Westermarck <fr...@mdh.se>.
Remy Maucherat wrote:
> > Actually I'm experiencing that problem using Sun:s 1.4 (1.4.0-beta-b65)
> > under RedHat Linux 7.0/2.2.19. So the statement that the problem doesn't
> > occur using the JDK 1.4 is not entirely true.
> Really ?
> I thought that was supposed to be fixed now ...
> Is b65 beta 1 or beta 2 ? My beta 2 for Windows reads b77.
1.4.0-beta-b65 is beta 1, and that one did have the same problem as
1.2.x and 1.3.x.
I realized that I might have forgot to get the latest JDK-beta so I
downloaded and installed beta2 (b77) and that one doesn't suffer from
that problem...
Re: Encrypted session cookies?
Posted by "Craig R. McClanahan" <cr...@apache.org>.
The Cookie.setSecure() method does *not* encrypt anything. It merely sets
a flag that tells the browser to only return this cookie on a secure
session.
If you don't want your session IDs to be snooped, you should always run
across SSL.
Craig McClanahan
On Mon, 15 Oct 2001, Frederick N. Brier wrote:
> Date: Mon, 15 Oct 2001 23:49:12 -0400
> From: Frederick N. Brier <fb...@multideck.com>
> Reply-To: tomcat-user@jakarta.apache.org
> To: tomcat-user@jakarta.apache.org
> Subject: Encrypted session cookies?
>
> It seemed to me session IDs stored in cookies could be exploited since they
> can be transmitted in the clear. Then I saw this message from a year ago
> which talked about exploiting unencrypted cookies.
>
> http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg00423.html
>
> It appears that Catalina session Cookie(s) are encrypted [ setSecure() ] if
> the when the session is created that Request is also "secure"
> [WarpResponse.java, line 220]. However, if the session has already been
> created, and then a person logs in, the session cookie would not be
> setSecure(). Is this correct? Is there an easy way to set it up so the
> session Cookie(s) are always encrypted? Thank you.
>
>
Encrypted session cookies?
Posted by "Frederick N. Brier" <fb...@multideck.com>.
It seemed to me session IDs stored in cookies could be exploited since they
can be transmitted in the clear. Then I saw this message from a year ago
which talked about exploiting unencrypted cookies.
http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg00423.html
It appears that Catalina session Cookie(s) are encrypted [ setSecure() ] if
the when the session is created that Request is also "secure"
[WarpResponse.java, line 220]. However, if the session has already been
created, and then a person logs in, the session cookie would not be
setSecure(). Is this correct? Is there an easy way to set it up so the
session Cookie(s) are always encrypted? Thank you.
Re: 4.0.1 just cores
Posted by Remy Maucherat <rm...@home.com>.
> Remy Maucherat wrote:
>
> > Hi,
> >
> > I've just added the Linux related info on the download page.
> > http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/
> >
> > Note: The problem could also have happened with 4.0, but not nearly as
> > reliably.
>
>
> Actually I'm experiencing that problem using Sun:s 1.4 (1.4.0-beta-b65)
> under RedHat Linux 7.0/2.2.19. So the statement that the problem doesn't
> occur using the JDK 1.4 is not entirely true.
Really ?
I thought that was supposed to be fixed now ...
Is b65 beta 1 or beta 2 ? My beta 2 for Windows reads b77.
Remy
Re: 4.0.1 just cores
Posted by Fredrik Westermarck <fr...@mdh.se>.
Remy Maucherat wrote:
> Hi,
>
> I've just added the Linux related info on the download page.
> http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/
>
> Note: The problem could also have happened with 4.0, but not nearly as
> reliably.
Actually I'm experiencing that problem using Sun:s 1.4 (1.4.0-beta-b65)
under RedHat Linux 7.0/2.2.19. So the statement that the problem doesn't
occur using the JDK 1.4 is not entirely true.
Re: 4.0.1 just cores
Posted by Remy Maucherat <rm...@home.com>.
Hi,
I've just added the Linux related info on the download page.
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/
Note: The problem could also have happened with 4.0, but not nearly as
reliably.
Remy
Re: 4.0.1 just cores
Posted by Paul DuBois <pa...@snake.net>.
At 5:18 PM -0700 10/15/01, Remy Maucherat wrote:
> > Ok, so I can get 4.0 working no problem with the latest Sun JDK on Linux
>> RH7.1. However 4.0.1 just cores when I try to start it. There do not seem
>> to be any errors but I can send the core file to someone if they want it.
>> :)
>
>To quote the release notes:
>
>-------------------------------
>Linux and Sun JDK 1.2.x - 1.3.x:
>-------------------------------
>
>Virtual machine crashes can be experienced when using certain combinations
>of
>kernel / glibc under Linux with Sun Hotspot 1.2 to 1.3. The crashes were
>reported to occur mostly on startup. Sun JDK 1.4 does not exhibit the
>problems,
>and neither does IBM JDK for Linux.
>
>The problems can be fixed by reducing the default stack size. At bash shell,
>do "ulimit -s 2048"; use "limit stacksize 2048" for tcsh.
Just to report in: Changing the stack size worked for me under RedHat 7.0.
Thanks!
>
>GLIBC 2.2 / Linux 2.4 users should also define an environment variable:
>export LD_ASSUME_KERNEL=2.2.5
>
>Remy
--
Paul DuBois, paul@snake.net
Re: 4.0.1 just cores
Posted by Remy Maucherat <rm...@home.com>.
> Ok, so I can get 4.0 working no problem with the latest Sun JDK on Linux
> RH7.1. However 4.0.1 just cores when I try to start it. There do not seem
> to be any errors but I can send the core file to someone if they want it.
> :)
To quote the release notes:
-------------------------------
Linux and Sun JDK 1.2.x - 1.3.x:
-------------------------------
Virtual machine crashes can be experienced when using certain combinations
of
kernel / glibc under Linux with Sun Hotspot 1.2 to 1.3. The crashes were
reported to occur mostly on startup. Sun JDK 1.4 does not exhibit the
problems,
and neither does IBM JDK for Linux.
The problems can be fixed by reducing the default stack size. At bash shell,
do "ulimit -s 2048"; use "limit stacksize 2048" for tcsh.
GLIBC 2.2 / Linux 2.4 users should also define an environment variable:
export LD_ASSUME_KERNEL=2.2.5
Remy
Re: 4.0.1 just cores
Posted by Remy Maucherat <rm...@home.com>.
> Works for me (with the .tar.gz download):
>
> Linux Red Hat 7.1
>
> java version "1.3.1"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-b24)
> Java HotSpot(TM) Client VM (build 1.3.1-b24, mixed mode)
>
> I downloaded this in mid-May or thereabouts). I'm doing some research to
> see if this is more or less recent than 1.3.1_01.
If Tomcat 4.0.1 crashes under Linux, use the workaround described in the
release notes.
I think the problem is related to the change from Crimson to Xerces.
Remy
> On Mon, 15 Oct 2001, Paul DuBois wrote:
>
> > Date: Mon, 15 Oct 2001 16:47:45 -0500
> > From: Paul DuBois <pa...@snake.net>
> > Reply-To: tomcat-user@jakarta.apache.org
> > To: tomcat-user@jakarta.apache.org
> > Subject: Re: 4.0.1 just cores
> >
> > >I am using Sun's JVM. 4.0 seems to work fine so far, 4.0.1 just cores.
> > >
> > >Linux RedHat 7.1
> > >
> > >java version "1.3.1_01"
> > >Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_01)
> > >Java HotSpot(TM) Client VM (build 1.3.1_01, mixed mode)
> >
> > Ditto. Also happens with RedHat 7.0.
> >
> > --
> > Paul DuBois, paul@snake.net
> >
>
Re: 4.0.1 just cores
Posted by "Craig R. McClanahan" <cr...@apache.org>.
Works for me (with the .tar.gz download):
Linux Red Hat 7.1
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-b24)
Java HotSpot(TM) Client VM (build 1.3.1-b24, mixed mode)
I downloaded this in mid-May or thereabouts). I'm doing some research to
see if this is more or less recent than 1.3.1_01.
Craig
On Mon, 15 Oct 2001, Paul DuBois wrote:
> Date: Mon, 15 Oct 2001 16:47:45 -0500
> From: Paul DuBois <pa...@snake.net>
> Reply-To: tomcat-user@jakarta.apache.org
> To: tomcat-user@jakarta.apache.org
> Subject: Re: 4.0.1 just cores
>
> >I am using Sun's JVM. 4.0 seems to work fine so far, 4.0.1 just cores.
> >
> >Linux RedHat 7.1
> >
> >java version "1.3.1_01"
> >Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_01)
> >Java HotSpot(TM) Client VM (build 1.3.1_01, mixed mode)
>
> Ditto. Also happens with RedHat 7.0.
>
> --
> Paul DuBois, paul@snake.net
>
Re: 4.0.1 just cores
Posted by Paul DuBois <pa...@snake.net>.
>I am using Sun's JVM. 4.0 seems to work fine so far, 4.0.1 just cores.
>
>Linux RedHat 7.1
>
>java version "1.3.1_01"
>Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_01)
>Java HotSpot(TM) Client VM (build 1.3.1_01, mixed mode)
Ditto. Also happens with RedHat 7.0.
--
Paul DuBois, paul@snake.net
Re: 4.0.1 just cores
Posted by Pier Fumagalli <pi...@betaversion.org>.
Terrence Martin at twm139@its.to wrote:
> BTW: Has anyone gotten this error when trying to start apache?
>
> Invalid port number (p<1) No "Port" statement found. I am trying to
> compile the connector myself now from source to see if that helps.
>
> My apache conf is out of the server.xml
>
> LoadModule webapp_module libexec/mod_webapp.so
> WebAppConnection warpConnection warp localhost:8008
> WebAppDeploy examples warpConnection /examples/
>
> If I remove the last line the problem goes away. Am I missing something?
Yes... Just got a report for that...
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4042
Pier
Re: 4.0.1 just cores
Posted by Terrence Martin <tw...@its.to>.
I am using Sun's JVM. 4.0 seems to work fine so far, 4.0.1 just cores.
Linux RedHat 7.1
java version "1.3.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_01)
Java HotSpot(TM) Client VM (build 1.3.1_01, mixed mode)
Just downloaded this one recently. I might try a slightly older 1.3.1 once
I get 4.0 working with warp.
BTW: Has anyone gotten this error when trying to start apache?
Invalid port number (p<1) No "Port" statement found. I am trying to
compile the connector myself now from source to see if that helps.
My apache conf is out of the server.xml
LoadModule webapp_module libexec/mod_webapp.so
WebAppConnection warpConnection warp localhost:8008
WebAppDeploy examples warpConnection /examples/
If I remove the last line the problem goes away. Am I missing something?
Terrence
On Mon, 15 Oct 2001, Pier Fumagalli wrote:
> Terrence Martin at twm139@its.to wrote:
>
> > Ok, so I can get 4.0 working no problem with the latest Sun JDK on Linux
> > RH7.1. However 4.0.1 just cores when I try to start it. There do not seem
> > to be any errors but I can send the core file to someone if they want it.
> > :)
>
> It WHAT? Cores? Darnnnnnn... What VM are you using? (It's a VM issue, not a
> Tomcat one IMHO)
>
> Pier
>
Re: 4.0.1 just cores
Posted by Pier Fumagalli <pi...@betaversion.org>.
Terrence Martin at twm139@its.to wrote:
> Ok, so I can get 4.0 working no problem with the latest Sun JDK on Linux
> RH7.1. However 4.0.1 just cores when I try to start it. There do not seem
> to be any errors but I can send the core file to someone if they want it.
> :)
It WHAT? Cores? Darnnnnnn... What VM are you using? (It's a VM issue, not a
Tomcat one IMHO)
Pier
4.0.1 just cores
Posted by Terrence Martin <tw...@its.to>.
Ok, so I can get 4.0 working no problem with the latest Sun JDK on Linux
RH7.1. However 4.0.1 just cores when I try to start it. There do not seem
to be any errors but I can send the core file to someone if they want it.
:)
Cheers,
Terrence
Re: Problems loading server.xml in Tomcat 4.0.1
Posted by Terrence Martin <tw...@its.to>.
I have narrowed the issue down to an incompatibility between the IBM JDK
1.3 and Tomcat. I have switched to Suns JDK 1.3.1_01 for linux and now it
seems to be working. I do not discount that it is a JDK issue but it is
worth mentioning I think as something to look out for.
Cheers,
Terrence
On Mon, 15 Oct 2001, Terrence Martin wrote:
> I get the following error when I try to run tomcat 4.0.1. The error shows
> up in catalina.out.
>
> Basically it looks like tomcat cannot find its config file. However ls
> seems to find it fine. Anyone else have this problem? I will note that I
> have made no changes to tomcat, just untar'd it and tried to run it.
>
> Tomcats error
>
> PARSE error at line 0 column 0 of
> /home/local/tomcat-4.0.1/bin/./../conf/server.xml
> org.xml.sax.SAXParseException: File
> "file:/home/local/tomcat-4.0.1/bin/./../conf/server.xml" not found.
> Catalina.start: org.xml.sax.SAXParseException: File
> "file:/home/local/tomcat-4.0.1/bin/./../conf/server.xml" not found.
> org.xml.sax.SAXParseException: File
> "file:/home/local/tomcat-4.0.1/bin/./../conf/server.xml" not found.
> at java.lang.Throwable.<init>(Throwable.java:96)
> at java.lang.Exception.<init>(Exception.java:44)
> at org.xml.sax.SAXException.<init>(SAXException.java:45)
> at org.xml.sax.SAXParseException.<init>(SAXParseException.java:56)
> at
> org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1202)
> at
> org.apache.xerces.readers.DefaultEntityHandler.startReadingFromDocument(DefaultEntityHandler.java:512)
> at
> org.apache.xerces.framework.XMLParser.parseSomeSetup(XMLParser.java:312)
> at
> org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1080)
> at
> org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.java:223)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:290)
> at
> org.apache.catalina.util.xml.XmlMapper.readXml(XmlMapper.java:228)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:725)
> at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
> at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
> at java.lang.reflect.Method.invoke(Native Method)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
>
>
> My own ls
>
> user@host ~$ ls -l /home/local/tomcat-4.0.1/bin/./../conf/server.xml
> -rw-r--r-- 1 root root 15743 Oct 14 12:15
> /home/local/tomcat-4.0.1/bin/./../conf/server.xml
>
> Cheers,
>
> Terrence
>