Re: Junk characters in SOAP request after upgrade to tomcat 9.0.31

[Naveen Kumar]

Hi All,

Can someone please help on this ? It is in production and affecting many
customers. Upgrading tomcat is a big task.
Any pointers will be really appreciated.

Thanks
Naveen

On Wed, Jun 10, 2020 at 4:24 PM Naveen Kumar  wrote:

> Hi Luis,
>
> Thanks for your suggestion.
> But I am wondering what has changed in 9.0.31. Because my webapp works
> perfectly fine in 9.0.24 and 9.0.35.
>
> Thanks
> Naveen
>
> On Wed, Jun 10, 2020 at 2:52 PM Luis Rodríguez Fernández <
> uo67...@gmail.com> wrote:
>
>> Hello Naveen,
>>
>> Recently we have had a similar issue migrating a webapp from another
>> application server to tomcat. We solved it specifying
>> UTF-8 in the
>> web.xml descriptor.
>>
>> You can read here [1] the long story :)
>>
>> Hope it helps,
>>
>> Luis
>>
>> [1] https://cwiki.apache.org/confluence/display/TOMCAT/Character+Encoding
>>
>>
>> El mié., 10 jun. 2020 a las 11:08, Naveen Kumar ()
>> escribió:
>>
>> > Hi All,
>> >
>> > I have a webapp A which has few SOAP services and I consume those
>> services
>> > from webapp B.
>> > I started getting below error since I upgraded the tomcat to 9.0.31
>> (from
>> > 9.0.24):
>> > com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync Couldn't create
>> SOAP
>> > message due to exception: XML reader error:
>> > javax.xml.stream.XMLStreamException: java.io.EOFException: Unexpected
>> EOF
>> >
>> > Then I wrote a filter at webapp A to intercept the request and I could
>> see
>> > that some junk characters are added in the SOAP request.
>> >
>> > If I upgrade tomcat to 9.0.35, the error disappears.
>> >
>> > Problematic request:
>> > LoggingFilter.doFilter - The servlet  request soap mapping  body is:à
>>  8Ï
>> > S(http://schemas.xmlsoap.org/soap/envelope/ð??? Envelope??? Body8Ï ns13
>> >
>> > Correct request:
>> > The servlet  request soap mapping  body is:> > encoding='UTF-8'?>> >
>> > Does anyone know what could be the possible reason for this?
>> >
>> > Thanks in advance.
>> > - Naveen
>> >
>>
>>
>> --
>>
>> "Ever tried. Ever failed. No matter. Try Again. Fail again. Fail better."
>>
>> - Samuel Beckett
>>
>

Re: tomcat 9.0 doesn't load the ECDSA keystore. (ver # 9.0.24)

[Madhan Raj]

Hi Chris,

Just attached the outputs logs and my server.xml including my ecdsa cert.
in keystoreand s_client outputs.txt file i have attached all the required
cert and keystore outputs.

What client are you using to attempt the handshake? i am using openssl
command line utility to test

What error(s) do you get with the handshake?  secure negotiation not
supported

If you configure *only* ESDSA, can you handshake? Or does ECDSA never
work?   correct ECDSA never work for me.
here in my case on port 443 i hosted only ECDSA keystore and on 8443 i have
hosted RSA keystore.
8443 works like charm and 443 is down

Thanks,
Madhan.

On Thu, Jun 11, 2020 at 1:47 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Madhan,
>
> On 6/10/20 22:08, Madhan Raj wrote:
> > Any insights please .
>
> How did you create your certificate?
>
> What are the details of your certificate and key? For example, which
> curve are you using? How many key bits? What type of signature on the
> certificate? What is the alias for that certificate in your keystore?
> Does it match what you have configured in Tomcat? Do you have a
> password on your keystore? Are you setting that correctly in your
>  element? (I see no password in your posted config.)
>
> What client are you using to attempt the handshake?
>
> What error(s) do you get with the handshake?
>
> If you configure *only* ESDSA, can you handshake? Or does ECDSA never
> work?
>
> You haven't give us much to go on, other than "I can't get ESDSA to
> work" when it's pretty clear others can get it to work.
>
> - -chris
>
> > On Thu, 4 Jun, 2020, 11:12 pm Madhan Raj,  > > wrote:
> >
> > Hi Christopher,
> >
> > Yes you correct I can only complete a handshake with RSA cert, not
> > ECDSA cert. when i try to connect with ECDSA ciphers using
> > s_client negotiation fails. Madhan
> >
> > On Thu, Jun 4, 2020 at 12:41 PM Christopher Schultz
> >  > > wrote:
> >
> > Madhan,
> >
> > On 6/3/20 21:08, Madhan Raj wrote:
> >> OS - CentOS 7.6.1810( Core)
> >
> >> Below connector doesn't load my EC keystore whereas it works
> >> with RSA . Any insights please .
> >
> > When you say "doesn't load", what do you mean? Possible reasonable
> > responses are:
> >
> > 1. I can only complete a handshake with RSA cert, not ECDSA cert 2.
> > Error message (please post) 3. JVM crashes 4. OS crashes 5.
> > Universe ends (possible, but unlikely to be reproducible)
> >
> >> this is my connector tag  in server.xml  >> SSLEnabled="true" URIEncoding="UTF-8"  maxThreads="200"
> >> port="443" scheme="https" secure="true"
> >> protocol="org.apache.coyote.http11.Http11NioProtocol"
> >
> > sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementat
> >
> >
> ion"
> >
> >
> > disableUploadTimeout="true" enableLookups="false"
> > maxHttpHeaderSize="819 2"
> >> minSpareThreads="25">  >> certificateVerification="none" sessionTimeout="1800"
> >> protocols="TLSv1,TLSv1.1,TLSv1.2,TLSv1.3"
> >
> > ciphers="ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECD
> >
> >
> HE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:AES256-SHA:DHE-DS
> > S-AES256-SHA:AES128-SHA:DHE-RSA-AES128-SHA"
> >
> >
> > sessionCacheSize="1">
> >>  >
> > certificateKeystoreFile="/usr/local/platform/.security/tomcat-ECDSA/ce
> >
> >
> rts/tomcat-ECDSA.keystore"
> >
> >
> > certificateKeystorePassword="8o8yeAH2qSJbJ2sn"
> >> certificateKeystoreType="PKCS12" type="EC"/> 
> >> 
> >
> >> tomcat start up command used :- /home/tomcat/tomcat -user tomcat
> >> -home /usr/local/thirdparty/java/j2sdk -pidfile
> >> /usr/local/thirdparty/jakarta-tomcat/conf/tomcat.pid -procname
> >> /home/tomcat/tomcat -outfile
> >> /usr/local/thirdparty/jakarta-tomcat/logs/catalina.out -errfile
> >> &1 -Djdk.tls.ephemeralDHKeySize=2048
> >> -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
> >> -Dorg.apache.catalina.security.SecurityListener.UMASK=0027
> >
> > -Djava.util.logging.config.file=/usr/local/thirdparty/jakarta-tomcat/c
> >
> >
> onf/logging.properties
> >
> >
> > -
> > -agentlib:jdwp=transport=dt_socket,address=localhost:8000,server=y,sus
> pe
> >
> >
> nd=n
> >> -XX:+UseParallelGC -XX:GCTimeRatio=99 -XX:MaxGCPauseMillis=80
> >> -Xmx1824m -Xms256m
> >> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> >>
> >>
> - -cp
> >
> > /usr/local/thirdparty/jakarta-tomcat/bin/bootstrap.jar:/usr/local/thir
> >
> >
> dparty/jakarta-tomcat/bin/tomcat-juli.jar
> >
> >
> > -
> > -Djava.security.policy==/usr/local/thirdparty/jakarta-tomcat/conf/cata
> li
> >
> >
> na.policy
> >> -Dcatalina.base=/usr/local/thirdparty/jakarta-tomcat
> >> -Dcatalina.home=/usr/local/thirdparty/jakarta-tomcat
> >> -Djava.io.tmpdir=/usr/local/thirdparty/jakarta-tomcat/temp
> >> org.apache.catalina.startup.Bootstrap start'
> >
> >> JAVA_OPTS= -Djava.library.path=$LD_LIBRARY_PATH
> >> -Djavax.net.ssl.sessionCacheSize=1
> >
> 

RE: Warning "AJP13 protocol: Reuse is set to false" written logs every second of every day. Please help.

[jonmcalexander]

Perhaps also compare your logging sensitivity between the servers.


Dream * Excel * Explore * Inspire
Jon McAlexander
Asst Vice President

Middleware Product Engineering
Enterprise CIO | Platform Services | Middleware | Infrastructure Solutions

8080 Cobblestone Rd | Urbandale, IA 50322
MAC: F4469-010
Tel 515-988-2508 | Cell 515-988-2508

jonmcalexan...@wellsfargo.com


This message may contain confidential and/or privileged information. If you are 
not the addressee or authorized to receive this for the addressee, you must not 
use, copy, disclose, or take any action based on this message or any 
information herein. If you have received this message in error, please advise 
the sender immediately by reply e-mail and delete this message. Thank you for 
your cooperation.

-Original Message-
From: Christopher Schultz  
Sent: Thursday, June 11, 2020 12:55 PM
To: users@tomcat.apache.org
Subject: Re: Warning "AJP13 protocol: Reuse is set to false" written logs every 
second of every day. Please help.

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Alfred,

On 6/11/20 11:57, Alfred Bakia wrote:
> Hi Everyone,
>
> This is my very first mail to the users list since joining yesterday. 
> Not an auspicious start. But I hope I will be able to contribute in 
> future. I seek your help for a persistent issue in one of our 
> ColdFusion instances.
>
> Description of issue: ColdFusion 2018 is an application server that 
> uses Tomcat 9.0.21. Our ColdFusion installation consists of instances. 
> The instances are independent application servers, each with its own 
> Tomcat installation and Java Virtual Machine. The Java version is 
> 11.0.7.
>
> Each ColdFusion instance serves web content via the web server IIS.
> We have configured an AJP connector for the communication between 
> Tomcat and IIS. The relevant settings are
>
>
> *   In server.xml
>
>  redirectPort="8445" protocol="AJP/1.3" tomcatAuthentication="false"
> maxThreads="500" packetSize="65535"/>
>
>
> *   In isapi_redirect.properties
>
> iis_buffer_enable= true
>
>
> *   In workers.properties
>
> worker.list=sr1studierdr1
>
> worker.sr1studierdr1.type=ajp13
>
> worker.sr1studierdr1.host=localhost
>
> worker.sr1studierdr1.port=8012
>
> worker.sr1studierdr1.connection_pool_size=800
>
> worker.sr1studierdr1.connection_pool_timeout=60
>
> worker.sr1studierdr1.max_reuse_connections=400''
>
> On one of the instances (name: 'sr1studierdr1'), the following WARNING 
> is written to isapi_redirect.log every second or so:
>
>
> *   [Thu Jun 11 16:44:57.739 2020] [11308:15392] [warn]
> ajp_process_callback::jk_ajp_common.c (2242): (sr1studierdr1) AJP13
> protocol: Reuse is set to false
>
> Nevertheless, the application seems to work as intended.
>
> We're at a loss why this is happening only to this particular 
> instance. There are no such warnings in other instances that share 
> exactly the same settings.
>
> Do you know what is causing the warning, "AJP13 protocol: Reuse is set 
> to false", or how to solve this?

I have no idea, but Google seemed able to come up with this:

https://forums.iis.net/t/1229345.aspx?Error+AJP13+protocol+Reuse+is+set+
to+false+on+log+file+

Does that help at all?

Apache httpd configuration of mod_jk has a DisableReuse flag that can be set, 
but I don't see such a thing for IIS.

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7ib9wACgkQHPApP6U8
pFiTzxAAljUf3DhO5zCex044toYxhtsrjb0ARCpFggrOXWiKBHHAyvnsMe/d1CFb
Tp5BLQdoWD1qorCkXMvFAYAdFOcbgmxMuUb3dkyHiq9JMZxINz3vOUXGtyqKfTLd
IT8VZ+kUSUq3brcoqMdkCNNpILAVNprtwCJdMoPSilVufG2vksjbBS2PT6YzSsXS
EaOb138vVb82HA6vvtOsi9EbOvh1cRVhZ2sIQlvrYsoTjeRD4QmRbmIQw+TcMPag
gtZtf46TyAtQSOs1L50LxRL1YXQLpsFNLKMItgTXEcooA/0RXUK1p8uG3Mr4G2my
L88nDE7zNxbGUHVGmMDx7p8EN839xcI1fEZJWv9+hTP/GbnsWR8TFNxWbv3Jjn7U
sOayEP/bgrFivKof57owHOo1FzcKaNGciUSMTTtUKqjHv0UpgcFAP1dAl5Py2xc7
E/oIw8ulgkxzri7Ge+Tczkt9CQlZIai8ZeIqtHpXtMEO6WRyC6qUZEmjq2PDMQLz
8c1UFqnfKcGHNaHGgQBL4MPxvl/lyIRa0CtxP7NsytsCnBOWzpVRY1EV7G8595Kg
tAHDf3x/ogQFl/bRptRnoOU2pbd5VsFZpiEkoAntwdTV5pVZJfDAkbKNgrGdLI3/
Az7EIFdKrbNMk48fsHtdRnhLcGavqJ+x4dZ+U8xi2TcRcCe5xoQ=
=0ac3
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Warning "AJP13 protocol: Reuse is set to false" written logs every second of every day. Please help.

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Alfred,

On 6/11/20 11:57, Alfred Bakia wrote:
> Hi Everyone,
>
> This is my very first mail to the users list since joining
> yesterday. Not an auspicious start. But I hope I will be able to
> contribute in future. I seek your help for a persistent issue in
> one of our ColdFusion instances.
>
> Description of issue: ColdFusion 2018 is an application server that
> uses Tomcat 9.0.21. Our ColdFusion installation consists of
> instances. The instances are independent application servers, each
> with its own Tomcat installation and Java Virtual Machine. The Java
> version is 11.0.7.
>
> Each ColdFusion instance serves web content via the web server IIS.
> We have configured an AJP connector for the communication between
> Tomcat and IIS. The relevant settings are
>
>
> *   In server.xml
>
>  redirectPort="8445" protocol="AJP/1.3" tomcatAuthentication="false"
> maxThreads="500" packetSize="65535"/>
>
>
> *   In isapi_redirect.properties
>
> iis_buffer_enable= true
>
>
> *   In workers.properties
>
> worker.list=sr1studierdr1
>
> worker.sr1studierdr1.type=ajp13
>
> worker.sr1studierdr1.host=localhost
>
> worker.sr1studierdr1.port=8012
>
> worker.sr1studierdr1.connection_pool_size=800
>
> worker.sr1studierdr1.connection_pool_timeout=60
>
> worker.sr1studierdr1.max_reuse_connections=400''
>
> On one of the instances (name: 'sr1studierdr1'), the following
> WARNING is written to isapi_redirect.log every second or so:
>
>
> *   [Thu Jun 11 16:44:57.739 2020] [11308:15392] [warn]
> ajp_process_callback::jk_ajp_common.c (2242): (sr1studierdr1) AJP13
> protocol: Reuse is set to false
>
> Nevertheless, the application seems to work as intended.
>
> We're at a loss why this is happening only to this particular
> instance. There are no such warnings in other instances that share
> exactly the same settings.
>
> Do you know what is causing the warning, "AJP13 protocol: Reuse is
> set to false", or how to solve this?

I have no idea, but Google seemed able to come up with this:

https://forums.iis.net/t/1229345.aspx?Error+AJP13+protocol+Reuse+is+set+
to+false+on+log+file+

Does that help at all?

Apache httpd configuration of mod_jk has a DisableReuse flag that can
be set, but I don't see such a thing for IIS.

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7ib9wACgkQHPApP6U8
pFiTzxAAljUf3DhO5zCex044toYxhtsrjb0ARCpFggrOXWiKBHHAyvnsMe/d1CFb
Tp5BLQdoWD1qorCkXMvFAYAdFOcbgmxMuUb3dkyHiq9JMZxINz3vOUXGtyqKfTLd
IT8VZ+kUSUq3brcoqMdkCNNpILAVNprtwCJdMoPSilVufG2vksjbBS2PT6YzSsXS
EaOb138vVb82HA6vvtOsi9EbOvh1cRVhZ2sIQlvrYsoTjeRD4QmRbmIQw+TcMPag
gtZtf46TyAtQSOs1L50LxRL1YXQLpsFNLKMItgTXEcooA/0RXUK1p8uG3Mr4G2my
L88nDE7zNxbGUHVGmMDx7p8EN839xcI1fEZJWv9+hTP/GbnsWR8TFNxWbv3Jjn7U
sOayEP/bgrFivKof57owHOo1FzcKaNGciUSMTTtUKqjHv0UpgcFAP1dAl5Py2xc7
E/oIw8ulgkxzri7Ge+Tczkt9CQlZIai8ZeIqtHpXtMEO6WRyC6qUZEmjq2PDMQLz
8c1UFqnfKcGHNaHGgQBL4MPxvl/lyIRa0CtxP7NsytsCnBOWzpVRY1EV7G8595Kg
tAHDf3x/ogQFl/bRptRnoOU2pbd5VsFZpiEkoAntwdTV5pVZJfDAkbKNgrGdLI3/
Az7EIFdKrbNMk48fsHtdRnhLcGavqJ+x4dZ+U8xi2TcRcCe5xoQ=
=0ac3
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: tomcat 9.0 doesn't load the ECDSA keystore. (ver # 9.0.24)

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Madhan,

On 6/10/20 22:08, Madhan Raj wrote:
> Any insights please .

How did you create your certificate?

What are the details of your certificate and key? For example, which
curve are you using? How many key bits? What type of signature on the
certificate? What is the alias for that certificate in your keystore?
Does it match what you have configured in Tomcat? Do you have a
password on your keystore? Are you setting that correctly in your
 element? (I see no password in your posted config.)

What client are you using to attempt the handshake?

What error(s) do you get with the handshake?

If you configure *only* ESDSA, can you handshake? Or does ECDSA never
work?

You haven't give us much to go on, other than "I can't get ESDSA to
work" when it's pretty clear others can get it to work.

- -chris

> On Thu, 4 Jun, 2020, 11:12 pm Madhan Raj,  > wrote:
>
> Hi Christopher,
>
> Yes you correct I can only complete a handshake with RSA cert, not
> ECDSA cert. when i try to connect with ECDSA ciphers using
> s_client negotiation fails. Madhan
>
> On Thu, Jun 4, 2020 at 12:41 PM Christopher Schultz
>  > wrote:
>
> Madhan,
>
> On 6/3/20 21:08, Madhan Raj wrote:
>> OS - CentOS 7.6.1810( Core)
>
>> Below connector doesn't load my EC keystore whereas it works
>> with RSA . Any insights please .
>
> When you say "doesn't load", what do you mean? Possible reasonable
> responses are:
>
> 1. I can only complete a handshake with RSA cert, not ECDSA cert 2.
> Error message (please post) 3. JVM crashes 4. OS crashes 5.
> Universe ends (possible, but unlikely to be reproducible)
>
>> this is my connector tag  in server.xml > SSLEnabled="true" URIEncoding="UTF-8"  maxThreads="200"
>> port="443" scheme="https" secure="true"
>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>
> sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementat
>
>
ion"
>
>
> disableUploadTimeout="true" enableLookups="false"
> maxHttpHeaderSize="819 2"
>> minSpareThreads="25"> > certificateVerification="none" sessionTimeout="1800"
>> protocols="TLSv1,TLSv1.1,TLSv1.2,TLSv1.3"
>
> ciphers="ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECD
>
>
HE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:AES256-SHA:DHE-DS
> S-AES256-SHA:AES128-SHA:DHE-RSA-AES128-SHA"
>
>
> sessionCacheSize="1">
>> 
> certificateKeystoreFile="/usr/local/platform/.security/tomcat-ECDSA/ce
>
>
rts/tomcat-ECDSA.keystore"
>
>
> certificateKeystorePassword="8o8yeAH2qSJbJ2sn"
>> certificateKeystoreType="PKCS12" type="EC"/> 
>> 
>
>> tomcat start up command used :- /home/tomcat/tomcat -user tomcat
>> -home /usr/local/thirdparty/java/j2sdk -pidfile
>> /usr/local/thirdparty/jakarta-tomcat/conf/tomcat.pid -procname
>> /home/tomcat/tomcat -outfile
>> /usr/local/thirdparty/jakarta-tomcat/logs/catalina.out -errfile
>> &1 -Djdk.tls.ephemeralDHKeySize=2048
>> -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
>> -Dorg.apache.catalina.security.SecurityListener.UMASK=0027
>
> -Djava.util.logging.config.file=/usr/local/thirdparty/jakarta-tomcat/c
>
>
onf/logging.properties
>
>
> -
> -agentlib:jdwp=transport=dt_socket,address=localhost:8000,server=y,sus
pe
>
>
nd=n
>> -XX:+UseParallelGC -XX:GCTimeRatio=99 -XX:MaxGCPauseMillis=80
>> -Xmx1824m -Xms256m
>> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
>>
>>
- -cp
>
> /usr/local/thirdparty/jakarta-tomcat/bin/bootstrap.jar:/usr/local/thir
>
>
dparty/jakarta-tomcat/bin/tomcat-juli.jar
>
>
> -
> -Djava.security.policy==/usr/local/thirdparty/jakarta-tomcat/conf/cata
li
>
>
na.policy
>> -Dcatalina.base=/usr/local/thirdparty/jakarta-tomcat
>> -Dcatalina.home=/usr/local/thirdparty/jakarta-tomcat
>> -Djava.io.tmpdir=/usr/local/thirdparty/jakarta-tomcat/temp
>> org.apache.catalina.startup.Bootstrap start'
>
>> JAVA_OPTS= -Djava.library.path=$LD_LIBRARY_PATH
>> -Djavax.net.ssl.sessionCacheSize=1
>
> -Djavax.net.ssl.trustStore=/usr/local/platform/.security/tomcat/trust-
>
>
certs/tomcat-trust.keystore
>
>
> -Djavax.net.ssl.trustStorePassword=$TRUST_STORE_PASSWORD
>
> -XX:ErrorFile=$CATALINA_HOME/logs/diagnostic-info.jvm-crash.%p.tomcat.
>
>
txt
>
>
> -Dsun.zip.disableMemoryMapping=true
>> -XX:OnOutOfMemoryError=/home/tomcat/tomcat_diagnostics.sh
>> -XX:OnError=/home/tomcat/tomcat_diagnostics.sh $TOMCAT_JAVA_OPTS
>
>> Also can i have both RSA and ECDSA in a single keystore. Will
>> that work in tomcat 9?
>
> Yes. You have to use two  elements each with a
> different "type" and "certificateKeyAlias"
>
>> it used to work with tomat 7
>
> It still works with Tomcat 9.
>
> -chris
>
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7ibjkACgkQHPApP6U8
pFheVg//akO4QY2HP7S7zfseHqH3lb1ZsU4JxjGkCXNCGhX1lju3tAaGEqAEb/VG
ecnGaf/lvdhKlcNfI26ZdRjb0QM6CWwrhIvrnkRe8Yf5kYHFMRkIkllMMF27hhGd

Warning "AJP13 protocol: Reuse is set to false" written logs every second of every day. Please help.

[Alfred Bakia]

Hi Everyone,

This is my very first mail to the users list since joining yesterday. Not an 
auspicious start. But I hope I will be able to contribute in future. I seek 
your help for a persistent issue in one of our ColdFusion instances.

Description of issue:
ColdFusion 2018 is an application server that uses Tomcat 9.0.21. Our 
ColdFusion installation consists of instances. The instances are independent 
application servers, each with its own Tomcat installation and Java Virtual 
Machine. The Java version is 11.0.7.

Each ColdFusion instance serves web content via the web server IIS.  We have 
configured an AJP connector for the communication between Tomcat and IIS. The 
relevant settings are


  *   In server.xml




  *   In isapi_redirect.properties

iis_buffer_enable= true


  *   In workers.properties

worker.list=sr1studierdr1

worker.sr1studierdr1.type=ajp13

worker.sr1studierdr1.host=localhost

worker.sr1studierdr1.port=8012

worker.sr1studierdr1.connection_pool_size=800

worker.sr1studierdr1.connection_pool_timeout=60

worker.sr1studierdr1.max_reuse_connections=400''

On one of the instances (name: 'sr1studierdr1'), the following WARNING is 
written to isapi_redirect.log every second or so:


  *   [Thu Jun 11 16:44:57.739 2020] [11308:15392] [warn] 
ajp_process_callback::jk_ajp_common.c (2242): (sr1studierdr1) AJP13 protocol: 
Reuse is set to false

Nevertheless, the application seems to work as intended.

We're at a loss why this is happening only to this particular instance. There 
are no such warnings in other instances that share exactly the same settings.

Do you know what is causing the warning, "AJP13 protocol: Reuse is set to 
false", or how to solve this?

Kind regards,

Alfred

Re: context.xml under META-INF was not working

[Mark Thomas]

On 11/06/2020 16:09, S Abirami wrote:
> Hi Mark,
> 
> We don't have concern regarding the restart of tomcat for the changes in 
> context.xml. As our web application is mainly used to launch only the 
> standalone application.
> I have updated Cookieprocessor entry under the context tag in server.xml 
> specific to the application context path and it is working fine.

OK.

> But, I could see that tenable detects that all other web application also has 
> the SameSite attribute even though I have mentioned only in the specific 
> application context.
> It is really surprising me . But,  contrast ZAP tool reports for other 
> application it doesn't have SameSite attribute.

Sounds like you need to report a bug to tenable.

Mark


> 
> 
> Regards,
> Abirami.S
> 
> -Original Message-
> From: Mark Thomas  
> Sent: Thursday, June 11, 2020 8:19 PM
> To: Tomcat Users List 
> Subject: RE: context.xml under META-INF was not working
> 
> On June 11, 2020 2:32:51 PM UTC, S Abirami  
> wrote:
>> Hi Mark,
>>
>> We are using Apache Tomcat 9.0.33.
>> I am not seeing any exception regarding it.
> 
> That isn't what I asked. I asked for the log messages .
> 
> Fortunately, you have provided the information I was looking for below.
> 
>> In our application the web-application will not be located under the 
>> CATALINA_HOME/webapps location.
>> We placed in other location and mentioned the path in context tag with 
>> attributes path and docBase in server.xml .
> 
> It is strongly recommended you don't define Context elements in server.xml as 
> they only way to change them us to restart Tomcat.
> 
>> Here ,we mentioned the
>> deployOnStartUp as false.
>> Hence, I have created META-INF directory under the App_folder and 
>> created the context.xml and MANIFEST.MF files.
> 
> That won't work. The Context element in server.xml will be used. Either edit 
> the Context in server.xml or, better, move the Context definitions to 
> $CATALINA_BASE/conf///
> 
> Mark
> 
>>
>> Regarding logs, I could see only the below messages
>>
>> WARNING: Match [Server/Service/Engine/Host/Context] failed to set 
>> property [antiJARLocking] to [false]
>> WARNING: Match [Context/Manager] failed to set property [randomClass] 
>> to [java.security.SecureRandom]
>> SEVERE: Unknown default host [localhost] for service 
>> [StandardService[Catalina]]. Tomcat will not be able process HTTP/1.0 
>> requests that do not specify a host name.
>>
>>
>> Regards,
>> Abirami.S
>>
>> -Original Message-
>> From: Mark Thomas 
>> Sent: Thursday, June 11, 2020 7:27 PM
>> To: users@tomcat.apache.org
>> Subject: Re: context.xml under META-INF was not working
>>
>> On 11/06/2020 12:46, S Abirami wrote:
>>> Hi Mark,
>>>
>>> The below is the content of the context.xml
>>>
>>>   >> sameSiteCookies="strict"/> 
>>
>> That looks OK.
>>
>> What Tomcat version are you using?
>>
>> What do the logs say when the application is deployed? That will tell 
>> you where it is being deployed from which might suggest why that file 
>> isn't taking effect.
>>
>> Mark
>>
>>
>>>
>>> Regards,
>>> Abirami.S
>>> -Original Message-
>>> From: Mark Thomas 
>>> Sent: Thursday, June 11, 2020 5:12 PM
>>> To: users@tomcat.apache.org
>>> Subject: Re: context.xml under META-INF was not working
>>>
>>> On 11/06/2020 11:42, S Abirami wrote:
 Hi All,

 I want to configure SameSite attribute to the specific
>> web-application.
 For that, I have updated the context.xml of specific web application
>>
 located in /META-INF/context.xml

 


 It is not working. Only the changes in global context.xml is
>> working. Please guide to solve the issue.
>>>
>>> What is the full contents of /META-INF/context.xml
>>>
>>> Mark
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: context.xml under META-INF was not working

[S Abirami]

Hi Mark,

We don't have concern regarding the restart of tomcat for the changes in 
context.xml. As our web application is mainly used to launch only the 
standalone application.
I have updated Cookieprocessor entry under the context tag in server.xml 
specific to the application context path and it is working fine.

But, I could see that tenable detects that all other web application also has 
the SameSite attribute even though I have mentioned only in the specific 
application context.
It is really surprising me . But,  contrast ZAP tool reports for other 
application it doesn't have SameSite attribute.


Regards,
Abirami.S

-Original Message-
From: Mark Thomas  
Sent: Thursday, June 11, 2020 8:19 PM
To: Tomcat Users List 
Subject: RE: context.xml under META-INF was not working

On June 11, 2020 2:32:51 PM UTC, S Abirami  
wrote:
>Hi Mark,
>
>We are using Apache Tomcat 9.0.33.
>I am not seeing any exception regarding it.

That isn't what I asked. I asked for the log messages .

Fortunately, you have provided the information I was looking for below.

>In our application the web-application will not be located under the 
>CATALINA_HOME/webapps location.
>We placed in other location and mentioned the path in context tag with 
>attributes path and docBase in server.xml .

It is strongly recommended you don't define Context elements in server.xml as 
they only way to change them us to restart Tomcat.

> Here ,we mentioned the
>deployOnStartUp as false.
>Hence, I have created META-INF directory under the App_folder and 
>created the context.xml and MANIFEST.MF files.

That won't work. The Context element in server.xml will be used. Either edit 
the Context in server.xml or, better, move the Context definitions to 
$CATALINA_BASE/conf///

Mark

>
>Regarding logs, I could see only the below messages
>
>WARNING: Match [Server/Service/Engine/Host/Context] failed to set 
>property [antiJARLocking] to [false]
>WARNING: Match [Context/Manager] failed to set property [randomClass] 
>to [java.security.SecureRandom]
>SEVERE: Unknown default host [localhost] for service 
>[StandardService[Catalina]]. Tomcat will not be able process HTTP/1.0 
>requests that do not specify a host name.
>
>
>Regards,
>Abirami.S
>
>-Original Message-
>From: Mark Thomas 
>Sent: Thursday, June 11, 2020 7:27 PM
>To: users@tomcat.apache.org
>Subject: Re: context.xml under META-INF was not working
>
>On 11/06/2020 12:46, S Abirami wrote:
>> Hi Mark,
>> 
>> The below is the content of the context.xml
>> 
>>   > sameSiteCookies="strict"/> 
>
>That looks OK.
>
>What Tomcat version are you using?
>
>What do the logs say when the application is deployed? That will tell 
>you where it is being deployed from which might suggest why that file 
>isn't taking effect.
>
>Mark
>
>
>> 
>> Regards,
>> Abirami.S
>> -Original Message-
>> From: Mark Thomas 
>> Sent: Thursday, June 11, 2020 5:12 PM
>> To: users@tomcat.apache.org
>> Subject: Re: context.xml under META-INF was not working
>> 
>> On 11/06/2020 11:42, S Abirami wrote:
>>> Hi All,
>>>
>>> I want to configure SameSite attribute to the specific
>web-application.
>>> For that, I have updated the context.xml of specific web application
>
>>> located in /META-INF/context.xml
>>>
>>> 
>>>
>>>
>>> It is not working. Only the changes in global context.xml is
>working. Please guide to solve the issue.
>> 
>> What is the full contents of /META-INF/context.xml
>> 
>> Mark
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>> 
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>> 
>
>
>-
>To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: context.xml under META-INF was not working

[Mark Thomas]

On June 11, 2020 2:32:51 PM UTC, S Abirami  
wrote:
>Hi Mark,
>
>We are using Apache Tomcat 9.0.33.
>I am not seeing any exception regarding it.

That isn't what I asked. I asked for the log messages .

Fortunately, you have provided the information I was looking for below.

>In our application the web-application will not be located under the
>CATALINA_HOME/webapps location.
>We placed in other location and mentioned the path in context tag with
>attributes path and docBase in server.xml .

It is strongly recommended you don't define Context elements in server.xml as 
they only way to change them us to restart Tomcat.

> Here ,we mentioned the
>deployOnStartUp as false.
>Hence, I have created META-INF directory under the App_folder and
>created the context.xml and MANIFEST.MF files.

That won't work. The Context element in server.xml will be used. Either edit 
the Context in server.xml or, better, move the Context definitions to 
$CATALINA_BASE/conf///

Mark

>
>Regarding logs, I could see only the below messages
>
>WARNING: Match [Server/Service/Engine/Host/Context] failed to set
>property [antiJARLocking] to [false]
>WARNING: Match [Context/Manager] failed to set property [randomClass]
>to [java.security.SecureRandom]
>SEVERE: Unknown default host [localhost] for service
>[StandardService[Catalina]]. Tomcat will not be able process HTTP/1.0
>requests that do not specify a host name.
>
>
>Regards,
>Abirami.S
>
>-Original Message-
>From: Mark Thomas  
>Sent: Thursday, June 11, 2020 7:27 PM
>To: users@tomcat.apache.org
>Subject: Re: context.xml under META-INF was not working
>
>On 11/06/2020 12:46, S Abirami wrote:
>> Hi Mark,
>> 
>> The below is the content of the context.xml
>> 
>>   > sameSiteCookies="strict"/> 
>
>That looks OK.
>
>What Tomcat version are you using?
>
>What do the logs say when the application is deployed? That will tell
>you where it is being deployed from which might suggest why that file
>isn't taking effect.
>
>Mark
>
>
>> 
>> Regards,
>> Abirami.S
>> -Original Message-
>> From: Mark Thomas 
>> Sent: Thursday, June 11, 2020 5:12 PM
>> To: users@tomcat.apache.org
>> Subject: Re: context.xml under META-INF was not working
>> 
>> On 11/06/2020 11:42, S Abirami wrote:
>>> Hi All,
>>>
>>> I want to configure SameSite attribute to the specific
>web-application.
>>> For that, I have updated the context.xml of specific web application
>
>>> located in /META-INF/context.xml
>>>
>>> 
>>>
>>>
>>> It is not working. Only the changes in global context.xml is
>working. Please guide to solve the issue.
>> 
>> What is the full contents of /META-INF/context.xml
>> 
>> Mark
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>> 
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>> 
>
>
>-
>To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: context.xml under META-INF was not working

[S Abirami]

Hi Mark,

We are using Apache Tomcat 9.0.33.
I am not seeing any exception regarding it.

In our application the web-application will not be located under the 
CATALINA_HOME/webapps location.
We placed in other location and mentioned the path in context tag with 
attributes path and docBase in server.xml .Here ,we mentioned the 
deployOnStartUp as false.
Hence, I have created META-INF directory under the App_folder and created the 
context.xml and MANIFEST.MF files.

Regarding logs, I could see only the below messages

WARNING: Match [Server/Service/Engine/Host/Context] failed to set property 
[antiJARLocking] to [false]
WARNING: Match [Context/Manager] failed to set property [randomClass] to 
[java.security.SecureRandom]
SEVERE: Unknown default host [localhost] for service 
[StandardService[Catalina]]. Tomcat will not be able process HTTP/1.0 requests 
that do not specify a host name.


Regards,
Abirami.S

-Original Message-
From: Mark Thomas  
Sent: Thursday, June 11, 2020 7:27 PM
To: users@tomcat.apache.org
Subject: Re: context.xml under META-INF was not working

On 11/06/2020 12:46, S Abirami wrote:
> Hi Mark,
> 
> The below is the content of the context.xml
> 
>sameSiteCookies="strict"/> 

That looks OK.

What Tomcat version are you using?

What do the logs say when the application is deployed? That will tell you where 
it is being deployed from which might suggest why that file isn't taking effect.

Mark


> 
> Regards,
> Abirami.S
> -Original Message-
> From: Mark Thomas 
> Sent: Thursday, June 11, 2020 5:12 PM
> To: users@tomcat.apache.org
> Subject: Re: context.xml under META-INF was not working
> 
> On 11/06/2020 11:42, S Abirami wrote:
>> Hi All,
>>
>> I want to configure SameSite attribute to the specific web-application.
>> For that, I have updated the context.xml of specific web application 
>> located in /META-INF/context.xml
>>
>> 
>>
>>
>> It is not working. Only the changes in global context.xml is working. Please 
>> guide to solve the issue.
> 
> What is the full contents of /META-INF/context.xml
> 
> Mark
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: context.xml under META-INF was not working

[Mark Thomas]

On 11/06/2020 12:46, S Abirami wrote:
> Hi Mark,
> 
> The below is the content of the context.xml
> 
> 
> 
> 
> 

That looks OK.

What Tomcat version are you using?

What do the logs say when the application is deployed? That will tell
you where it is being deployed from which might suggest why that file
isn't taking effect.

Mark


> 
> Regards,
> Abirami.S
> -Original Message-
> From: Mark Thomas  
> Sent: Thursday, June 11, 2020 5:12 PM
> To: users@tomcat.apache.org
> Subject: Re: context.xml under META-INF was not working
> 
> On 11/06/2020 11:42, S Abirami wrote:
>> Hi All,
>>
>> I want to configure SameSite attribute to the specific web-application.
>> For that, I have updated the context.xml of specific web application located 
>> in /META-INF/context.xml
>>
>> 
>>
>>
>> It is not working. Only the changes in global context.xml is working. Please 
>> guide to solve the issue.
> 
> What is the full contents of /META-INF/context.xml
> 
> Mark
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: context.xml under META-INF was not working

[S Abirami]

Hi Mark,

The below is the content of the context.xml






Regards,
Abirami.S
-Original Message-
From: Mark Thomas  
Sent: Thursday, June 11, 2020 5:12 PM
To: users@tomcat.apache.org
Subject: Re: context.xml under META-INF was not working

On 11/06/2020 11:42, S Abirami wrote:
> Hi All,
> 
> I want to configure SameSite attribute to the specific web-application.
> For that, I have updated the context.xml of specific web application located 
> in /META-INF/context.xml
> 
> 
> 
> 
> It is not working. Only the changes in global context.xml is working. Please 
> guide to solve the issue.

What is the full contents of /META-INF/context.xml

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: context.xml under META-INF was not working

[Mark Thomas]

On 11/06/2020 11:42, S Abirami wrote:
> Hi All,
> 
> I want to configure SameSite attribute to the specific web-application.
> For that, I have updated the context.xml of specific web application located 
> in /META-INF/context.xml
> 
> 
> 
> 
> It is not working. Only the changes in global context.xml is working. Please 
> guide to solve the issue.

What is the full contents of /META-INF/context.xml

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: context.xml under META-INF was not working

[S Abirami]

Hi All,

I want to configure SameSite attribute to the specific web-application.
For that, I have updated the context.xml of specific web application located in 
/META-INF/context.xml




It is not working. Only the changes in global context.xml is working. Please 
guide to solve the issue.

Regards,
Abirami.S

Re: Tomcat 9.0.0 multiple thread issue

[Ripu Daman]

Sorry for late reply. We have fixed the issue. Kubernetes ingress file was
causing multiple requests to be sent over and over again. Proxy timeout
along with read and send timeouts were not present in that file. We have
added them and now the process is working fine allowing it to complete with
only one single thread.

Thank you all for your support.

Regards,
Ripu daman

On Tue 9 Jun, 2020, 10:20 PM Christopher Schultz, <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Ripu,
>
> On 6/9/20 08:03, Ripu Daman wrote:
> > Hello everyone,
> >
> > I work in an IT firm as a software engineer. I don't know whether
> > it's a right platform to ask questions based on personal projects
> > but i believe i will get some help from here.
> >
> > We are facing an issue regarding multiple threads being created for
> > a servlet execution running in tomcat 9.0.0
> >
> > Servlet's job is to publish customer leads to salesforce via soap
> > protocol. The logic has been designed in such a way that in a
> > single thread it can publish multiple leads to salesforce one by
> > one. However we recently migrated our java application to
> > kubernetes adopting containerized approach. Post this we are facing
> > an issue in which, when the process starts publishing leads to
> > salesforce one by one, after a few uploads a new thread gets
> > created and it starts the whole process from beginning and then
> > after a few seconds another thread kicks off repeating the whole
> > process. It keeps going on until session timeout exceeds and we get
> > a 504 error. But the upload process keeps going on in the
> > background and stops after 2-3 threads.
>
> Where is your queue stored?
>
> > Before moving to kubernetes, the process was working fine. In order
> > to serve multiple requests at the same time, servlet is not
> > designed to be thread safe.
>
> It's NOT designed to be thread-safe? I hope you meant it IS designed
> to be thread-safe.
>
> > But now we are facing this issue and unable to identify the root
> > cause.
> >
> > Here's a sample of threads from the logs : [http-nio-8080-exec-9]
> > INFO [http-nio-8080-exec-9] INFO [http-nio-8080-exec-9] INFO
> > [http-nio-8080-exec-7] INFO [http-nio-8080-exec-7] INFO
> > [http-nio-8080-exec-9] INFO [http-nio-8080-exec-9] INFO
> >
> > [http-nio-8080-exec-7] INFO [http-nio-8080-exec-7] INFO
> > [http-nio-8080-exec-7] INFO [http-nio-8080-exec-3] INFO
> > [http-nio-8080-exec-7] INFO [http-nio-8080-exec-3] INFO
>
> These are request-processing threads, so something is making HTTP
> requests to Tomcat to do that work.
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7fvbEACgkQHPApP6U8
> pFi9Uw/+O9Be+Bp7n8co6Rz7gkvtXZbKT5KlxpWtT3gVNluN4Lt824Hgb5C7wmMd
> AjZfvFO0yn1rIJsY+G0r/25lsdIVLZZW3ehM28eRgc+Up3sI66w8zvnOGhly7E6f
> CKvSKkINLrS9+BQ0HrLkqHxn+U4y2Ts8yfRZOelC8dGtFfj+U3cSsc75LGMUiREM
> SlYabv4dDzemfBqG/08zXfQ+laQStg9Cf+rY//ZZGnLWR74obJJB/rlhrNMAzND0
> qR5Z0LebYXGQEt6nElYtDtAosJlnlpX30fLX6aVwwIXfgPqeIgBF9PskIfwx1NU5
> sF3nIHO4wE+KsMqM22fqMOU6keBR/Ac8ktMEws/d6PEL1oXUhcsXMTulh6RrxHWA
> ImTlksYyIp54flIw3cwiooVW1VrgYQisIIucsWPzLSw7QsE9CyZADqYYm6N7Eo60
> VpdHAOLTX4zfJoMlf7NWuMdK8dFI8wkLUmCURxYkWysWx+MJ55BDgDy9kTw3QZoa
> lBZs9bPirGU8r7qmjbrj5L/Q0lpeqQSSj9ixBzAJKGBAYzYJHKWPpOcI2NW1hn6F
> vUi01xB67zXboH1EcLVHqMc9srA5UjaDKzwnCcwde1kBaxRbwHFIOq1s+BflXdEc
> 69gaaPqifMnp1pLaJoonPDyZ3QszSAm5SiUi6lKmofF0UBqTzYs=
> =SxID
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>