tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: TC 3.3, CVS: Tomcat shutdown
Date Wed, 07 Nov 2001 18:09:23 GMT
You need two threads since one is always supposed to be listening, and the
other does the actual shutting down.  Since the shutdown thread tries to
unblock the listening thread, it hangs if there isn't anyone listening.
----- Original Message -----
From: "Bojan Smojver" <bojan@binarix.com>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Sent: Wednesday, November 07, 2001 3:13 AM
Subject: Re: TC 3.3, CVS: Tomcat shutdown


> This was the config that didn't work:
> --------------------------------------------
>          <Ajp12Connector tomcatAuthentication="false"
>                          maxThreads="1"
>                          maxSpareThreads="1"
>                          minSpareThreads="1"
>                          port="8007"
>                          address="127.0.0.1"/>
> --------------------------------------------
>
> This is the configuration that also doesn't work:
> --------------------------------------------
>          <Ajp12Connector tomcatAuthentication="false"
>                          maxThreads="1"
>                          port="8007"
>                          address="127.0.0.1"/>
> --------------------------------------------
>
> because after adjustLimits() in ThreadPool.java, it comes down to my
> original configuration.
>
> This does work:
> --------------------------------------------
>          <Ajp12Connector tomcatAuthentication="false"
>                          port="8007"
>                          address="127.0.0.1"/>
> --------------------------------------------
>
> I'm not all that familiar with the threading code, but it seems as if
> the first two should work since there is one thread available (for
> shutdown only). And yet, they don't...
>
> This does work too:
> --------------------------------------------
>          <Ajp12Connector tomcatAuthentication="false"
>                          maxThreads="2"
>                          port="8007"
>                          address="127.0.0.1"/>
> --------------------------------------------
>
> So, there has to be at least 2 threads to shut TC 3.3 down. Don't know
> why, though. Any clues?
>
> Bojan
>
> Bojan Smojver wrote:
>
> > Quoting Bill Barker <wbarker@wilshire.com>:
> >
> >
> >>Works for me as well, but I use the default settings for
> >>Ajp12Interceptor.
> >>
> >
> > Aha, I have a few thingies there. I'll try to remove and recheck.
> >
> >
> >>The only relevant recent change is that ThreadPool no longer ignores
> >>your
> >>server.xml settings.  It's possible that we need to tweak the sanity
> >>checks
> >>in ThreadPool.
> >>
> >
> > I did a few stupid things before, so maybe I need to do some luser
sanity
> > checking ;-)
> >
> > Once I find out what happens with default settings, I'll know more. I'm
only
> > using Ajp12 to shut the thing down. Ajp13 is handling all requests. I'm
not
> > really sure if new Ajp13 has shutdown support (I saw something along
those lines
> > in Ajp13.java, but never really tried to understand it), but if it does,
I might
> > just drop Ajp12.
> >
> > Bojan
> >
> >
> >>----- Original Message -----
> >>From: "Larry Isaacs" <Larry.Isaacs@sas.com>
> >>To: "'Tomcat Developers List'" <tomcat-dev@jakarta.apache.org>
> >>Sent: Monday, November 05, 2001 6:30 AM
> >>Subject: RE: TC 3.3, CVS: Tomcat shutdown
> >>
> >>
> >>
> >>>I'm not seeing a problem on WinNT.
> >>>
> >>>Larry
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: Bojan Smojver [mailto:bojan@binarix.com]
> >>>>Sent: Monday, November 05, 2001 5:28 AM
> >>>>To: Tomcat Dev List
> >>>>Subject: TC 3.3, CVS: Tomcat shutdown
> >>>>
> >>>>
> >>>>Anyone having problems with TC 3.3 shutdown in the latest CVS
> >>>>snapshot?
> >>>>It suddenly stopped working for me...
> >>>>
> >>>>Bojan
> >>>>
> >>>>--
> >>>>To unsubscribe, e-mail:
> >>>><mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> >>>>For additional commands, e-mail:
> >>>><mailto:tomcat-dev-help@jakarta.apache.org>
> >>>>
> >>>--
> >>>To unsubscribe, e-mail:
> >>>
> >><mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> >>
> >>>For additional commands, e-mail:
> >>>
> >><mailto:tomcat-dev-help@jakarta.apache.org>
> >>
> >>>
> >>
> >>*----*
> >>
> >>This message is intended only for the use of the person(s) listed above
> >>
> >>as the intended recipient(s), and may contain information that is
> >>PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient,
> >>you may not read, copy, or distribute this message or any attachment.
> >>
> >>If you received this communication in error, please notify us
> >>immediately
> >>by e-mail and then delete all copies of this message and any
> >>attachments.
> >>
> >>
> >>In addition you should be aware that ordinary (unencrypted) e-mail sent
> >>
> >>through the Internet is not secure. Do not send confidential or
> >>sensitive
> >>information, such as social security numbers, account numbers, personal
> >>
> >>identification numbers and passwords, to us via ordinary (unencrypted)
> >>
> >>e-mail.
> >>
> >>--
> >>To unsubscribe, e-mail:
> >><mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> >>For additional commands, e-mail:
> >><mailto:tomcat-dev-help@jakarta.apache.org>
> >>
> >>
> >
> > --
> > To unsubscribe, e-mail:
<mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
<mailto:tomcat-dev-help@jakarta.apache.org>
> >
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:tomcat-dev-help@jakarta.apache.org>
>
>


*----*

This message is intended only for the use of the person(s) listed above 
as the intended recipient(s), and may contain information that is 
PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, 
you may not read, copy, or distribute this message or any attachment.  
If you received this communication in error, please notify us immediately 
by e-mail and then delete all copies of this message and any attachments.


In addition you should be aware that ordinary (unencrypted) e-mail sent 
through the Internet is not secure. Do not send confidential or sensitive 
information, such as social security numbers, account numbers, personal 
identification numbers and passwords, to us via ordinary (unencrypted) 
e-mail. 

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message