You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Larry Isaacs <La...@sas.com> on 2000/09/26 15:47:59 UTC
Showing internal request URI's in default responses
Hi,
Currently in Tomcat 3.2, DefaultCMSetter.NotFoundHandler and StatusHandler only show the original request. For "secure" responses this is appropriate, but during debugging, the request URI that gives rise the status code needs to be shown. This is especially true for "Not Found" errors.
I plan to add this and am interested in opinions about how to control the display of this information. I see updating ContextManager with one of the following options:
1) Use current showStackTraces attribute to control this too.
2) Rename showStackTraces to something more global, such as showDebugInfo, and use it to control this and stack traces.
3) Add a separate attribute, such as showDebugInfo, to control this.
I'm +1/2 on 2 and 3. Anyone with a preference, other option, or attribute name?
Cheers,
Larry
__________
Larry Isaacs
Larry.Isaacs@sas.com
SAS Institute Inc.
RE: Showing internal request URI's in default responses
Posted by Paulo Gaspar <pa...@krankikom.de>.
What is the advised way to restart an application?
Does that reload all the classes used by the application?
Thanks,
Paulo
> -----Original Message-----
> From: cmanolache@yahoo.com [mailto:cmanolache@yahoo.com]
> Sent: Wednesday, September 27, 2000 05:50
> To: tomcat-dev@jakarta.apache.org; pspeed@progeeks.com
> Subject: Re: Showing internal request URI's in default responses
>
>
> > Just wanted to add $0.02 about reloading. It is important
> > to note that reloading can be extremely important in a web hosting
> > environment where you don't want individual hostees(?) restarting
> > Tomcat.
>
> Yes, you're right, but it's a different problem.
>
> ( i.e. all you need in this case is a simple user interface to send
> restart signals to individual webapps ).
>
> Reloading works by detecting changes ( reading every file periodically -
> for a web hosting server it'll have a big impact to have so many disk
> accesses ), and restarting the web app if a change is detected.
>
> It's easy to just send the restart from an admin web page ( even the
> current admin allow to re-deploy an app ).
>
> > Also, even in our production site it's nice to be able to make
> > small updates without having to knock off all the users.
>
> It's a choice, and both options are valid. In both cases only the
> changed webapp should be restarted - the difference is how to tell tomcat
> to restart it - by an explicit action or by asking it to periodically
> check file access time.
>
>
> Costin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
Re: Showing internal request URI's in default responses
Posted by cm...@yahoo.com.
> Just wanted to add $0.02 about reloading. It is important
> to note that reloading can be extremely important in a web hosting
> environment where you don't want individual hostees(?) restarting
> Tomcat.
Yes, you're right, but it's a different problem.
( i.e. all you need in this case is a simple user interface to send
restart signals to individual webapps ).
Reloading works by detecting changes ( reading every file periodically -
for a web hosting server it'll have a big impact to have so many disk
accesses ), and restarting the web app if a change is detected.
It's easy to just send the restart from an admin web page ( even the
current admin allow to re-deploy an app ).
> Also, even in our production site it's nice to be able to make
> small updates without having to knock off all the users.
It's a choice, and both options are valid. In both cases only the
changed webapp should be restarted - the difference is how to tell tomcat
to restart it - by an explicit action or by asking it to periodically
check file access time.
Costin
Re: Showing internal request URI's in default responses
Posted by Paul Speed <ps...@progeeks.com>.
cmanolache@yahoo.com wrote:
>
> Hi Larry,
>
> +1 on whatever you choose, please update server.dtd and add the attribute
> in the default server.xml ( with the default value ).
>
> I like showDebugInfo - or even debugInfo, or even "developMode" ( that
> will also control the default for reloading !).
Just wanted to add $0.02 about reloading. It is important
to note that reloading can be extremely important in a web hosting
environment where you don't want individual hostees(?) restarting
Tomcat.
Also, even in our production site it's nice to be able to make
small updates without having to knock off all the users.
I understand you only intend to control the default reloading
with the developMode setting... and that there is still another way
to set reloading. I just wanted to point out that development is
not the only reason for reloading.
-Paul
>
> My only doubt is related with 3.2 release - even if this will probably
> have no effect, I'm afraid we'll not have a release as long as there are
> commits going in... I hope 3.3 feature freeze will happen in few weeks,
> and we're still in beta with 3.2.
>
> ( BTW, please don't forget to update 3.3 also !)
>
> Costin
>
> > 1) Use current showStackTraces attribute to control this too.
> >
> > 2) Rename showStackTraces to something more global, such as showDebugInfo, and use it to control this and stack traces.
> >
> > 3) Add a separate attribute, such as showDebugInfo, to control this.
> >
> > I'm +1/2 on 2 and 3. Anyone with a preference, other option, or attribute name?
> >
> > Cheers,
> > Larry
> >
> > __________
> > Larry Isaacs
> > Larry.Isaacs@sas.com
> > SAS Institute Inc.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
How to prevent auto reloading of changed JS page
Posted by Pankaj Malviya <pa...@internetdevices.com>.
Hi,
I have seen that a JSP page is automatically reloaded whenever it is
changed. I assume this has a cost in production server. I want to prevent
it. Till I restart my server the changed JSP should not be reloaded. I have
changed server.xml file to disable auto servlet loading in context but it
has affect only on servlet not on JSP. Any advice ?
Pankaj
Re: Showing internal request URI's in default responses
Posted by cm...@yahoo.com.
Hi Larry,
+1 on whatever you choose, please update server.dtd and add the attribute
in the default server.xml ( with the default value ).
I like showDebugInfo - or even debugInfo, or even "developMode" ( that
will also control the default for reloading !).
My only doubt is related with 3.2 release - even if this will probably
have no effect, I'm afraid we'll not have a release as long as there are
commits going in... I hope 3.3 feature freeze will happen in few weeks,
and we're still in beta with 3.2.
( BTW, please don't forget to update 3.3 also !)
Costin
> 1) Use current showStackTraces attribute to control this too.
>
> 2) Rename showStackTraces to something more global, such as showDebugInfo, and use it to control this and stack traces.
>
> 3) Add a separate attribute, such as showDebugInfo, to control this.
>
> I'm +1/2 on 2 and 3. Anyone with a preference, other option, or attribute name?
>
> Cheers,
> Larry
>
> __________
> Larry Isaacs
> Larry.Isaacs@sas.com
> SAS Institute Inc.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>