You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by David Soroko <da...@mannanetwork.com> on 2001/01/01 13:37:02 UTC

The significance of root context

I am trying to understand the significance of the "root" context in TC 3.2.

It seems that when no root context is defined i.e. when nothing is mapped to
"" path and
an unavailable resource is requested by a client, tomcat takes up 100% CPU
time and does not let go.


Must I always map some directory to the root context?




Steps to reproduce behavior in the standard TC 3.2 distribution:

* In server.xml comment out
<ContextInterceptor className="org.apache.tomcat.context.AutoSetup" />

(this has the effect that the webapps/ROOT is not mapped to "").

* Start TC

* Connect to http://localhost:8080

Note: the same behavior can be seen if webapps/ROOT is removed.





--

============================================
David Soroko
mailto:davids@mannanetwork.com
http://www.geocities.com/SiliconValley/Campus/1628/
Manna Inc.
============================================

Re: The significance of root context

Posted by Shawn McMurdo <sh...@lutris.com>.
The patch was sent as an attachment.
Here it is again, this time as "diff -u" instead of "diff -c"
and I have forced it to plain text only instead of both plain text
and html.
Hopefully that will come through ok.
Let me know if you still have any problems.
Shawn

Marc Saegesser wrote:

> Shawn,
>
> Would you please re-post the patch.  Provide the output of cvs diff -u as an
> attachment this time.  Your previous post included the patch embedded inside
> the email (which was HTML formatted) and was almost unreadable.
>
> -----Original Message-----
> From: Shawn McMurdo [mailto:shawn@lutris.com]
> Sent: Tuesday, January 02, 2001 1:03 PM
> To: tomcat-dev@jakarta.apache.org
> Subject: Re: The significance of root context
>
> Did you see my patch submitted to the list on 2000 Dec 23?
> I think it addresses this problem.
> Shawn
> David Soroko wrote:
>  Thanks --
> ============================================
> David Soroko
> mailto:davids@mannanetwork.com
> http://www.geocities.com/SiliconValley/Campus/1628/
> Manna Inc.
> ============================================
>
> -----Original Message-----
> From: Thom Park [mailto:tpark@inprise.com]
> Sent: Tuesday, January 02, 2001 1:42 AM
> To: tomcat-dev@jakarta.apache.org
> Subject: Re: The significance of root context
>
> This is a known bug in tomcat and is documented in the release notes - I got
> bit by this one as well ;-)
> -T.
> David Soroko wrote:
> I am trying to understand the significance of the "root" context in TC 3.2.
> It seems that when no root context is defined i.e. when nothing is mapped to
> "" path and
> an unavailable resource is requested by a client, tomcat takes up 100% CPU
> time and does not let go.
> Must I always map some directory to the root context?
>
> Steps to reproduce behavior in the standard TC 3.2 distribution:
> * In server.xml comment out
> <ContextInterceptor className="org.apache.tomcat.context.AutoSetup" />
> (this has the effect that the webapps/ROOT is not mapped to "").
> * Start TC
> * Connect to http://localhost:8080
> Note: the same behavior can be seen if webapps/ROOT is removed.
>
> --
> ============================================
> David Soroko
> mailto:davids@mannanetwork.com
> http://www.geocities.com/SiliconValley/Campus/1628/
> Manna Inc.
> ============================================
> --
> Shawn McMurdo              mailto:shawn@lutris.com
> Lutris Technologies        http://www.lutris.com
> Enhydra.Org                http://www.enhydra.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-dev-help@jakarta.apache.org

--
Shawn McMurdo              mailto:shawn@lutris.com
Lutris Technologies        http://www.lutris.com
Enhydra.Org                http://www.enhydra.org


RE: The significance of root context

Posted by Marc Saegesser <ma...@apropos.com>.
Shawn,

Would you please re-post the patch.  Provide the output of cvs diff -u as an
attachment this time.  Your previous post included the patch embedded inside
the email (which was HTML formatted) and was almost unreadable.


-----Original Message-----
From: Shawn McMurdo [mailto:shawn@lutris.com]
Sent: Tuesday, January 02, 2001 1:03 PM
To: tomcat-dev@jakarta.apache.org
Subject: Re: The significance of root context


Did you see my patch submitted to the list on 2000 Dec 23?
I think it addresses this problem.
Shawn
David Soroko wrote:
 Thanks --
============================================
David Soroko
mailto:davids@mannanetwork.com
http://www.geocities.com/SiliconValley/Campus/1628/
Manna Inc.
============================================

-----Original Message-----
From: Thom Park [mailto:tpark@inprise.com]
Sent: Tuesday, January 02, 2001 1:42 AM
To: tomcat-dev@jakarta.apache.org
Subject: Re: The significance of root context

This is a known bug in tomcat and is documented in the release notes - I got
bit by this one as well ;-)
-T.
David Soroko wrote:
I am trying to understand the significance of the "root" context in TC 3.2.
It seems that when no root context is defined i.e. when nothing is mapped to
"" path and
an unavailable resource is requested by a client, tomcat takes up 100% CPU
time and does not let go.
Must I always map some directory to the root context?


Steps to reproduce behavior in the standard TC 3.2 distribution:
* In server.xml comment out
<ContextInterceptor className="org.apache.tomcat.context.AutoSetup" />
(this has the effect that the webapps/ROOT is not mapped to "").
* Start TC
* Connect to http://localhost:8080
Note: the same behavior can be seen if webapps/ROOT is removed.



--
============================================
David Soroko
mailto:davids@mannanetwork.com
http://www.geocities.com/SiliconValley/Campus/1628/
Manna Inc.
============================================
--
Shawn McMurdo              mailto:shawn@lutris.com
Lutris Technologies        http://www.lutris.com
Enhydra.Org                http://www.enhydra.org



Re: The significance of root context

Posted by Shawn McMurdo <sh...@lutris.com>.
Did you see my patch submitted to the list on 2000 Dec 23?
I think it addresses this problem.
Shawn

David Soroko wrote:

>  Thanks --
>
> ============================================
> David Soroko
> mailto:davids@mannanetwork.com
> http://www.geocities.com/SiliconValley/Campus/1628/
> Manna Inc.
> ============================================
>
>
>      -----Original Message-----
>      From: Thom Park [mailto:tpark@inprise.com]
>      Sent: Tuesday, January 02, 2001 1:42 AM
>      To: tomcat-dev@jakarta.apache.org
>      Subject: Re: The significance of root context
>
>      This is a known bug in tomcat and is documented in the release
>      notes - I got bit by this one as well ;-)
>
>      -T.
>
>      David Soroko wrote:
>
>     > I am trying to understand the significance of the "root" context
>     > in TC 3.2.
>     >
>     > It seems that when no root context is defined i.e. when nothing
>     > is mapped to "" path and
>     > an unavailable resource is requested by a client, tomcat takes
>     > up 100% CPU time and does not let go.
>     >
>     > Must I always map some directory to the root context?
>     >
>     >
>     >
>     > Steps to reproduce behavior in the standard TC 3.2 distribution:
>     >
>     > * In server.xml comment out
>     > <ContextInterceptor
>     > className="org.apache.tomcat.context.AutoSetup" />
>     >
>     > (this has the effect that the webapps/ROOT is not mapped to "").
>     >
>     > * Start TC
>     >
>     > * Connect to http://localhost:8080
>     >
>     > Note: the same behavior can be seen if webapps/ROOT is removed.
>     >
>     >
>     >
>     >
>     > --
>     >
>     > ============================================
>     > David Soroko
>     > mailto:davids@mannanetwork.com
>     > http://www.geocities.com/SiliconValley/Campus/1628/
>     > Manna Inc.
>     > ============================================
>
--
Shawn McMurdo              mailto:shawn@lutris.com
Lutris Technologies        http://www.lutris.com
Enhydra.Org                http://www.enhydra.org


RE: The significance of root context

Posted by David Soroko <da...@mannanetwork.com>.
Thanks


--

============================================
David Soroko
mailto:davids@mannanetwork.com <ma...@mannanetwork.com>
http://www.geocities.com/SiliconValley/Campus/1628/
<http://www.geocities.com/SiliconValley/Campus/1628/>
Manna Inc.
============================================


-----Original Message-----
From: Thom Park [mailto:tpark@inprise.com]
Sent: Tuesday, January 02, 2001 1:42 AM
To: tomcat-dev@jakarta.apache.org
Subject: Re: The significance of root context


This is a known bug in tomcat and is documented in the release notes - I got
bit by this one as well ;-)

-T.


David Soroko wrote:


I am trying to understand the significance of the "root" context in TC 3.2.


It seems that when no root context is defined i.e. when nothing is mapped to
"" path and
an unavailable resource is requested by a client, tomcat takes up 100% CPU
time and does not let go.


Must I always map some directory to the root context?




Steps to reproduce behavior in the standard TC 3.2 distribution:


* In server.xml comment out
<ContextInterceptor className="org.apache.tomcat.context.AutoSetup" />


(this has the effect that the webapps/ROOT is not mapped to "").


* Start TC


* Connect to http://localhost:8080 <http://localhost:8080>


Note: the same behavior can be seen if webapps/ROOT is removed.





--


============================================
David Soroko
mailto:davids@mannanetwork.com <ma...@mannanetwork.com>
http://www.geocities.com/SiliconValley/Campus/1628/
<http://www.geocities.com/SiliconValley/Campus/1628/>
Manna Inc.
============================================


Re: The significance of root context

Posted by Thom Park <tp...@inprise.com>.
This is a known bug in tomcat and is documented in the release notes - I
got bit by this one as well ;-)

-T.

David Soroko wrote:

> I am trying to understand the significance of the "root" context in TC
> 3.2.
>
> It seems that when no root context is defined i.e. when nothing is
> mapped to "" path and
> an unavailable resource is requested by a client, tomcat takes up 100%
> CPU time and does not let go.
>
> Must I always map some directory to the root context?
>
>
>
> Steps to reproduce behavior in the standard TC 3.2 distribution:
>
> * In server.xml comment out
> <ContextInterceptor className="org.apache.tomcat.context.AutoSetup" />
>
> (this has the effect that the webapps/ROOT is not mapped to "").
>
> * Start TC
>
> * Connect to http://localhost:8080
>
> Note: the same behavior can be seen if webapps/ROOT is removed.
>
>
>
>
> --
>
> ============================================
> David Soroko
> mailto:davids@mannanetwork.com
> http://www.geocities.com/SiliconValley/Campus/1628/
> Manna Inc.
> ============================================