RE: Different shutdown behavior of httpConnector in TC403 (graceful) and TC406 (reckless)

[Ralph Einfeldt <ra...@uptime-isc.de>]

I think that the waay of TC406 is better. This way you can 
have both solutions.

If you have threads that do something important that has 
to be finished before termination, just don't define them 
as daemon threads.

> -----Original Message-----
> From: Frank.Strecker@arcor.net [mailto:Frank.Strecker@arcor.net]
> Sent: Wednesday, June 04, 2003 12:07 PM
> To: tomcat-user@jakarta.apache.org
> Subject: Different shutdown behavior of httpConnector in TC403
> (graceful) and TC406 (reckless)
> 
<snip/>
> It seems to that -  while TC 403 waits "gracefully" for the 
> work on a request to
> be finished (even forever) - TC 406 will wait 5 secs only and 
> then shutdown without
> any respect to the work done in the processors background threads.
> 
<snip/>
> 
> So, my primary question is this one: Did I overlook a point, 
> in particular: Is there a way to configure the shutdown behavior 
> in TC 406 top wait for the background threads to finish?
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: Tomcat bug? WinXp, IE6, Tomcat 4.1.24, JSPTags

[Dominic Parry <do...@rucus.ru.ac.za>]

What is the page Title? could you give the whole error output?
  ----- Original Message ----- 
  From: Graham Reeds 
  To: Tomcat Users List 
  Sent: Thursday, June 05, 2003 11:55 AM
  Subject: Tomcat bug? WinXp, IE6, Tomcat 4.1.24, JSPTags


  I dunno if this is the correct mailing since I have only just joined, but...

  I am using Tomcat 4.1.24, the JDK 1.3.1.08.  Unfortunately I can't change
  the version numbers since our client is using this version.

  I am new to Java and currently feeling my way round JSP Tags and the found
  what I believe is a bug.  I have a very simple tag called name in my tld xml
  file.

  Ergo the getter and setter code is: getName() and setName();

  Change the tag name to pageTitle you'd expect the getter and setter to be
  getPageTitle() and setPageTitle().  This compiles fine but running it in my
  browser (IE6) causes an 'org.apache.jasper.JasperException' to fire.  Change
  the getter and setter to getpageTitle(), etc. and it works fine.

  I would of assumed that it changed 'name' to a capital it would
  automatically change the first letter of 'pageTitle' to capitals.  Is this
  standard behaviour?

  --

  Graham Reeds,
  grahamr@omnieng.co.uk | http://omnieng.co.uk




  ---------------------------------------------------------------------
  To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
  For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Tomcat bug? WinXp, IE6, Tomcat 4.1.24, JSPTags

[Graham Reeds <gr...@omnieng.co.uk>]

I dunno if this is the correct mailing since I have only just joined, but...

I am using Tomcat 4.1.24, the JDK 1.3.1.08.  Unfortunately I can't change
the version numbers since our client is using this version.

I am new to Java and currently feeling my way round JSP Tags and the found
what I believe is a bug.  I have a very simple tag called name in my tld xml
file.

Ergo the getter and setter code is: getName() and setName();

Change the tag name to pageTitle you'd expect the getter and setter to be
getPageTitle() and setPageTitle().  This compiles fine but running it in my
browser (IE6) causes an 'org.apache.jasper.JasperException' to fire.  Change
the getter and setter to getpageTitle(), etc. and it works fine.

I would of assumed that it changed 'name' to a capital it would
automatically change the first letter of 'pageTitle' to capitals.  Is this
standard behaviour?

--

Graham Reeds,
grahamr@omnieng.co.uk | http://omnieng.co.uk




---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org