You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Rallavagu <ra...@gmail.com> on 2016/10/31 17:59:25 UTC
currentThreadCount and currentThreadsBusy
All,
Tomcat 7.0.70 with bio connector
I have been monitoring JMX for "currentThreadCount" and
"currentThreadsBusy". If I understand correctly, currentThreadCount
would not exceed "maxThreads" configuration and "currentThreadsBusy"
apparently shows "busy" threads at that time. I am wondering if there is
a "timeout" (or other config/parameter) for not busy threads (for long
time) to be removed so currentThreadCount would be reduced. Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: currentThreadCount and currentThreadsBusy
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Rallavagu,
On 10/31/16 4:02 PM, Rallavagu wrote:
> On 10/31/16 12:54 PM, Mark Thomas wrote:
>> On 31/10/2016 19:52, Rallavagu wrote:
>>> As per
>>> https://tomcat.apache.org/tomcat-7.0-doc/config/executor.html
>>> it appears "maxIdleTime" could be what I am looking for. Is
>>> there a corresponding config parameter for internal thread
>>> pool?
>>
>> Which part of "hard-coded" wasn't clear?
>
> Well, I was not sure if is referred to "maxIdleTimeout" or not and
> I am not seeing thread count to diminish hence had to ask. So, I
> guess the recommendation is to use Executor instead?
Yes: use of an explicit <Executor> is recommended.
I was under the impression that a non-explicit <Executor> would never
retire threads, but I had (and still have) never checked the code. I
didn't realize that they would time-out after 60 seconds and be
evicted from the thread pool.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJYGNmUAAoJEBzwKT+lPKRYA1AQALcvgriRX6CYHDVramLfubd+
3s/CiECcGZxCtnqMpc5UMC972/MXFzwDZ0QbPR/piMjoAGpMdHruRxNmdWK/mBDv
IAFu0c8rrtITcox26WoYzJjq7DckbKB0VDU4uoLqwv5Aih9/6GiaX3EIf9sSLN1P
ODEdk9lDpsFhNVP+GAI/Ls/+xfLb3Rr5DVSQmpImSwgIRiiF3XzU6SOaV6cI0Pg5
ew6lduHDDwl33Rzy0IoXjgHUYnM5h117SLB/muZEQ4WZWPMsax1kn7zhfjhdPXHF
1vyDP00yiCjYfnnkoicUoPgjTzztKw5mSUsS0p/bqV2vgd2kkgipVfq6kBIWHaAr
dvvc7p2RpCBqHdJAN/EgddG6Og/HrL0/NEuXT5HN8Cu3TIUVIJL0Q/+WmBf1DaIs
APnpN19aFcUQY3Ok1iVeKeHhIiXCDcMWUy9rx1giErpHIB20CQaBsUd35Zxj2EqJ
YrULvPAxc39fIrolMhq63gaNhLMLTKHvDxsSUh8SmKosQLPrQcHZMVbRUl4WMQzC
TEF73QL/vC5LProuwLwTIqYDE0FOwIitVAmrryPnw7lfss3bMvPNTs/sk9pwcZZ7
pUEV4CJlSwO0TA40BJMSY6ywVcSOz3Q2TJtlKzy0o4Wqr+2XXEC2noB/Bh1dW8hS
cqGGfMLE89NyeFadIpMp
=MTSU
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: currentThreadCount and currentThreadsBusy
Posted by Rallavagu <ra...@gmail.com>.
On 10/31/16 12:54 PM, Mark Thomas wrote:
> On 31/10/2016 19:52, Rallavagu wrote:
>> As per https://tomcat.apache.org/tomcat-7.0-doc/config/executor.html it
>> appears "maxIdleTime" could be what I am looking for. Is there a
>> corresponding config parameter for internal thread pool?
>
> Which part of "hard-coded" wasn't clear?
Well, I was not sure if is referred to "maxIdleTimeout" or not and I am
not seeing thread count to diminish hence had to ask. So, I guess the
recommendation is to use Executor instead?
>
> Mark
>
>
>>
>> On 10/31/16 12:44 PM, Mark Thomas wrote:
>>> On 31/10/2016 19:38, Rallavagu wrote:
>>>> Here is the configuration snippet.
>>>>
>>>> <!--The connectors can use a shared executor, you can define one or more
>>>> named thread pools-->
>>>> <!--
>>>> <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
>>>> maxThreads="150" minSpareThreads="4"/>
>>>> -->
>>>>
>>>> <Connector port="28080" protocol="HTTP/1.1" URIEncoding="UTF-8"
>>>> maxThreads="500"
>>>> connectionTimeout="20000"
>>>> redirectPort="28443" />
>>>> <!-- A "Connector" using the shared thread pool-->
>>>> <!--
>>>> <Connector executor="tomcatThreadPool"
>>>> port="28080" protocol="HTTP/1.1"
>>>> connectionTimeout="20000"
>>>> redirectPort="28443" />
>>>> -->
>>>>
>>>> As you can see, _not_ using executor. Thanks.
>>>
>>> When using the internal thread pool, that delay is hard-coded to 60s. If
>>> you want to configure it, use an Executor.
>>>
>>> Mark
>>>
>>>
>>>>
>>>> On 10/31/16 11:58 AM, Christopher Schultz wrote:
>>>> Rallavagu,
>>>>
>>>> On 10/31/16 1:59 PM, Rallavagu wrote:
>>>>>>> All,
>>>>>>>
>>>>>>> Tomcat 7.0.70 with bio connector
>>>>>>>
>>>>>>> I have been monitoring JMX for "currentThreadCount" and
>>>>>>> "currentThreadsBusy". If I understand correctly,
>>>>>>> currentThreadCount would not exceed "maxThreads" configuration and
>>>>>>> "currentThreadsBusy" apparently shows "busy" threads at that time.
>>>>>>> I am wondering if there is a "timeout" (or other config/parameter)
>>>>>>> for not busy threads (for long time) to be removed so
>>>>>>> currentThreadCount would be reduced. Thanks.
>>>>
>>>> Are you using an <Executor>? Perhaps you could post your <Connector>
>>>> and also <Executor> configuration if you are using one.
>>>>
>>>> -chris
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: currentThreadCount and currentThreadsBusy
Posted by Mark Thomas <ma...@apache.org>.
On 31/10/2016 19:52, Rallavagu wrote:
> As per https://tomcat.apache.org/tomcat-7.0-doc/config/executor.html it
> appears "maxIdleTime" could be what I am looking for. Is there a
> corresponding config parameter for internal thread pool?
Which part of "hard-coded" wasn't clear?
Mark
>
> On 10/31/16 12:44 PM, Mark Thomas wrote:
>> On 31/10/2016 19:38, Rallavagu wrote:
>>> Here is the configuration snippet.
>>>
>>> <!--The connectors can use a shared executor, you can define one or more
>>> named thread pools-->
>>> <!--
>>> <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
>>> maxThreads="150" minSpareThreads="4"/>
>>> -->
>>>
>>> <Connector port="28080" protocol="HTTP/1.1" URIEncoding="UTF-8"
>>> maxThreads="500"
>>> connectionTimeout="20000"
>>> redirectPort="28443" />
>>> <!-- A "Connector" using the shared thread pool-->
>>> <!--
>>> <Connector executor="tomcatThreadPool"
>>> port="28080" protocol="HTTP/1.1"
>>> connectionTimeout="20000"
>>> redirectPort="28443" />
>>> -->
>>>
>>> As you can see, _not_ using executor. Thanks.
>>
>> When using the internal thread pool, that delay is hard-coded to 60s. If
>> you want to configure it, use an Executor.
>>
>> Mark
>>
>>
>>>
>>> On 10/31/16 11:58 AM, Christopher Schultz wrote:
>>> Rallavagu,
>>>
>>> On 10/31/16 1:59 PM, Rallavagu wrote:
>>>>>> All,
>>>>>>
>>>>>> Tomcat 7.0.70 with bio connector
>>>>>>
>>>>>> I have been monitoring JMX for "currentThreadCount" and
>>>>>> "currentThreadsBusy". If I understand correctly,
>>>>>> currentThreadCount would not exceed "maxThreads" configuration and
>>>>>> "currentThreadsBusy" apparently shows "busy" threads at that time.
>>>>>> I am wondering if there is a "timeout" (or other config/parameter)
>>>>>> for not busy threads (for long time) to be removed so
>>>>>> currentThreadCount would be reduced. Thanks.
>>>
>>> Are you using an <Executor>? Perhaps you could post your <Connector>
>>> and also <Executor> configuration if you are using one.
>>>
>>> -chris
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: currentThreadCount and currentThreadsBusy
Posted by Rallavagu <ra...@gmail.com>.
As per https://tomcat.apache.org/tomcat-7.0-doc/config/executor.html it
appears "maxIdleTime" could be what I am looking for. Is there a
corresponding config parameter for internal thread pool?
On 10/31/16 12:44 PM, Mark Thomas wrote:
> On 31/10/2016 19:38, Rallavagu wrote:
>> Here is the configuration snippet.
>>
>> <!--The connectors can use a shared executor, you can define one or more
>> named thread pools-->
>> <!--
>> <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
>> maxThreads="150" minSpareThreads="4"/>
>> -->
>>
>> <Connector port="28080" protocol="HTTP/1.1" URIEncoding="UTF-8"
>> maxThreads="500"
>> connectionTimeout="20000"
>> redirectPort="28443" />
>> <!-- A "Connector" using the shared thread pool-->
>> <!--
>> <Connector executor="tomcatThreadPool"
>> port="28080" protocol="HTTP/1.1"
>> connectionTimeout="20000"
>> redirectPort="28443" />
>> -->
>>
>> As you can see, _not_ using executor. Thanks.
>
> When using the internal thread pool, that delay is hard-coded to 60s. If
> you want to configure it, use an Executor.
>
> Mark
>
>
>>
>> On 10/31/16 11:58 AM, Christopher Schultz wrote:
>> Rallavagu,
>>
>> On 10/31/16 1:59 PM, Rallavagu wrote:
>>>>> All,
>>>>>
>>>>> Tomcat 7.0.70 with bio connector
>>>>>
>>>>> I have been monitoring JMX for "currentThreadCount" and
>>>>> "currentThreadsBusy". If I understand correctly,
>>>>> currentThreadCount would not exceed "maxThreads" configuration and
>>>>> "currentThreadsBusy" apparently shows "busy" threads at that time.
>>>>> I am wondering if there is a "timeout" (or other config/parameter)
>>>>> for not busy threads (for long time) to be removed so
>>>>> currentThreadCount would be reduced. Thanks.
>>
>> Are you using an <Executor>? Perhaps you could post your <Connector>
>> and also <Executor> configuration if you are using one.
>>
>> -chris
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: currentThreadCount and currentThreadsBusy
Posted by Rallavagu <ra...@gmail.com>.
On 10/31/16 12:44 PM, Mark Thomas wrote:
> On 31/10/2016 19:38, Rallavagu wrote:
>> Here is the configuration snippet.
>>
>> <!--The connectors can use a shared executor, you can define one or more
>> named thread pools-->
>> <!--
>> <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
>> maxThreads="150" minSpareThreads="4"/>
>> -->
>>
>> <Connector port="28080" protocol="HTTP/1.1" URIEncoding="UTF-8"
>> maxThreads="500"
>> connectionTimeout="20000"
>> redirectPort="28443" />
>> <!-- A "Connector" using the shared thread pool-->
>> <!--
>> <Connector executor="tomcatThreadPool"
>> port="28080" protocol="HTTP/1.1"
>> connectionTimeout="20000"
>> redirectPort="28443" />
>> -->
>>
>> As you can see, _not_ using executor. Thanks.
>
> When using the internal thread pool, that delay is hard-coded to 60s. If
> you want to configure it, use an Executor.
>
> Mark
Thanks Mark. What I am noticing is that "currentThreadCount" remain same
even after when there is not much of load.
>
>
>>
>> On 10/31/16 11:58 AM, Christopher Schultz wrote:
>> Rallavagu,
>>
>> On 10/31/16 1:59 PM, Rallavagu wrote:
>>>>> All,
>>>>>
>>>>> Tomcat 7.0.70 with bio connector
>>>>>
>>>>> I have been monitoring JMX for "currentThreadCount" and
>>>>> "currentThreadsBusy". If I understand correctly,
>>>>> currentThreadCount would not exceed "maxThreads" configuration and
>>>>> "currentThreadsBusy" apparently shows "busy" threads at that time.
>>>>> I am wondering if there is a "timeout" (or other config/parameter)
>>>>> for not busy threads (for long time) to be removed so
>>>>> currentThreadCount would be reduced. Thanks.
>>
>> Are you using an <Executor>? Perhaps you could post your <Connector>
>> and also <Executor> configuration if you are using one.
>>
>> -chris
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: currentThreadCount and currentThreadsBusy
Posted by Mark Thomas <ma...@apache.org>.
On 31/10/2016 19:38, Rallavagu wrote:
> Here is the configuration snippet.
>
> <!--The connectors can use a shared executor, you can define one or more
> named thread pools-->
> <!--
> <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
> maxThreads="150" minSpareThreads="4"/>
> -->
>
> <Connector port="28080" protocol="HTTP/1.1" URIEncoding="UTF-8"
> maxThreads="500"
> connectionTimeout="20000"
> redirectPort="28443" />
> <!-- A "Connector" using the shared thread pool-->
> <!--
> <Connector executor="tomcatThreadPool"
> port="28080" protocol="HTTP/1.1"
> connectionTimeout="20000"
> redirectPort="28443" />
> -->
>
> As you can see, _not_ using executor. Thanks.
When using the internal thread pool, that delay is hard-coded to 60s. If
you want to configure it, use an Executor.
Mark
>
> On 10/31/16 11:58 AM, Christopher Schultz wrote:
> Rallavagu,
>
> On 10/31/16 1:59 PM, Rallavagu wrote:
>>>> All,
>>>>
>>>> Tomcat 7.0.70 with bio connector
>>>>
>>>> I have been monitoring JMX for "currentThreadCount" and
>>>> "currentThreadsBusy". If I understand correctly,
>>>> currentThreadCount would not exceed "maxThreads" configuration and
>>>> "currentThreadsBusy" apparently shows "busy" threads at that time.
>>>> I am wondering if there is a "timeout" (or other config/parameter)
>>>> for not busy threads (for long time) to be removed so
>>>> currentThreadCount would be reduced. Thanks.
>
> Are you using an <Executor>? Perhaps you could post your <Connector>
> and also <Executor> configuration if you are using one.
>
> -chris
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: currentThreadCount and currentThreadsBusy
Posted by Rallavagu <ra...@gmail.com>.
Here is the configuration snippet.
<!--The connectors can use a shared executor, you can define one or more
named thread pools-->
<!--
<Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
maxThreads="150" minSpareThreads="4"/>
-->
<Connector port="28080" protocol="HTTP/1.1" URIEncoding="UTF-8"
maxThreads="500"
connectionTimeout="20000"
redirectPort="28443" />
<!-- A "Connector" using the shared thread pool-->
<!--
<Connector executor="tomcatThreadPool"
port="28080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="28443" />
-->
As you can see, _not_ using executor. Thanks.
On 10/31/16 11:58 AM, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Rallavagu,
>
> On 10/31/16 1:59 PM, Rallavagu wrote:
>> All,
>>
>> Tomcat 7.0.70 with bio connector
>>
>> I have been monitoring JMX for "currentThreadCount" and
>> "currentThreadsBusy". If I understand correctly,
>> currentThreadCount would not exceed "maxThreads" configuration and
>> "currentThreadsBusy" apparently shows "busy" threads at that time.
>> I am wondering if there is a "timeout" (or other config/parameter)
>> for not busy threads (for long time) to be removed so
>> currentThreadCount would be reduced. Thanks.
>
> Are you using an <Executor>? Perhaps you could post your <Connector>
> and also <Executor> configuration if you are using one.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYF5RsAAoJEBzwKT+lPKRYOMIP/Axsb/+n3iy/PvgM2/zibK2X
> aCiFjwH1bdInzCnPwaO02B6rYTgxAIEjgcBSMCTjBh7cyB9Okq1I5yo1ylVOHprd
> GECbu401or1FpVfj4JPLL/yK8bS2m8cZ+s+JL4SKkhYIxzeNL/bm89v+tEXmAViw
> 6WmvgxF7zqswQBzkmkk2Z+20JnbqsLvXhXang25/BeAPFt9Q/ojHz96N8i3ENDMf
> 5YiXXukGIZjtLFqtsA1V+YpuehkzYYJxkgO2viipKP1B8hOHggjh+GpV4N0AXbwv
> a//NcYW5AgdH38jWueEdvrTftfX+6PMc804HcdCVUkJK64zsyR3YwapyW8rZSir8
> UOaELgfh/TOF0z7LK4hIRBQwZgKczj9IKJcWZsT/JYVmt3HLVyNqwo0iIw2iYbgQ
> 44iirJy40apjPabC7I9fJY8hRrv2JIrQg0rti2CEFH7LFGXsCaNayveKngZlPOy9
> 6/ZrzF2OVkzhDGV2WwCzjPak7t20OvN8F3+KLu+ldPrbWNKw15DbBJCeFUs0U02E
> Z5gFRvP9CiVV3qywlq4E/qtDNkMNAW/N+RBxn/KjSFosHIuZ2CwlVB993/FsDbQW
> d1hev6Xshr2STepoyn4++/PQ5mdrQRPOK+lMKBXtLrKRdzauAUnt3Dkgm204z4o6
> vTqaaUzfscZFXPWxgdCM
> =X1cd
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: currentThreadCount and currentThreadsBusy
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Rallavagu,
On 10/31/16 1:59 PM, Rallavagu wrote:
> All,
>
> Tomcat 7.0.70 with bio connector
>
> I have been monitoring JMX for "currentThreadCount" and
> "currentThreadsBusy". If I understand correctly,
> currentThreadCount would not exceed "maxThreads" configuration and
> "currentThreadsBusy" apparently shows "busy" threads at that time.
> I am wondering if there is a "timeout" (or other config/parameter)
> for not busy threads (for long time) to be removed so
> currentThreadCount would be reduced. Thanks.
Are you using an <Executor>? Perhaps you could post your <Connector>
and also <Executor> configuration if you are using one.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJYF5RsAAoJEBzwKT+lPKRYOMIP/Axsb/+n3iy/PvgM2/zibK2X
aCiFjwH1bdInzCnPwaO02B6rYTgxAIEjgcBSMCTjBh7cyB9Okq1I5yo1ylVOHprd
GECbu401or1FpVfj4JPLL/yK8bS2m8cZ+s+JL4SKkhYIxzeNL/bm89v+tEXmAViw
6WmvgxF7zqswQBzkmkk2Z+20JnbqsLvXhXang25/BeAPFt9Q/ojHz96N8i3ENDMf
5YiXXukGIZjtLFqtsA1V+YpuehkzYYJxkgO2viipKP1B8hOHggjh+GpV4N0AXbwv
a//NcYW5AgdH38jWueEdvrTftfX+6PMc804HcdCVUkJK64zsyR3YwapyW8rZSir8
UOaELgfh/TOF0z7LK4hIRBQwZgKczj9IKJcWZsT/JYVmt3HLVyNqwo0iIw2iYbgQ
44iirJy40apjPabC7I9fJY8hRrv2JIrQg0rti2CEFH7LFGXsCaNayveKngZlPOy9
6/ZrzF2OVkzhDGV2WwCzjPak7t20OvN8F3+KLu+ldPrbWNKw15DbBJCeFUs0U02E
Z5gFRvP9CiVV3qywlq4E/qtDNkMNAW/N+RBxn/KjSFosHIuZ2CwlVB993/FsDbQW
d1hev6Xshr2STepoyn4++/PQ5mdrQRPOK+lMKBXtLrKRdzauAUnt3Dkgm204z4o6
vTqaaUzfscZFXPWxgdCM
=X1cd
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org