Regarding ECJ jar with tomcat 8.5.13

[Rathore, Rajendra]

Hi Team,

We are facing compatibility issue with latest ECJ jar with Drools, currently we 
are using tomcat 8.5.13 with 4.6.1 ECJ jar, is it possible that we move to 
4.5.1 ECJ jar with tomcat 8.5.13, is there any compatibility issue happen, 
Please confirm. I am also going to check the same on my local environment also.

Your assistance help a lot for us.

Thanks and Regards,
Rajendra Rathore
9922701491

RE: Regarding ECJ jar with tomcat 8.5.13

[Rathore, Rajendra]

So it is ok to use ECJ 4.5.1 version jar with tomcat 8.5.13, am I right?

Thanks and Regards,
Rajendra Rathore
9922701491


-Original Message-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] 
Sent: Tuesday, April 25, 2017 12:42 PM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Regarding ECJ jar with tomcat 8.5.13

2017-04-25 8:48 GMT+03:00 Rathore, Rajendra <rarath...@ptc.com>:
> Hi Team,
>
> We are facing compatibility issue with latest ECJ jar with Drools, currently 
> we are using tomcat 8.5.13 with 4.6.1 ECJ jar, is it possible that we move to 
> 4.5.1 ECJ jar with tomcat 8.5.13, is there any compatibility issue happen, 
> Please confirm. I am also going to check the same on my local environment 
> also.
>
> Your assistance help a lot for us.

I think that there should not be any issues.
4.6 may add additional constant for "Java 9" --source version, but I think that 
the API used by Tomcat is the same.
(If it is different, you'll see right away).

You may try the current 4.6 which I think is 4.6.3. If it fixes your issue, 
feel free to file a Bugzilla entry.

See old Bugzilla issues for Tomcat for download links.

Best regards,
Konstantin Kolinko

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

precompile JSPs failure issue - Tomcat community

[Rathore, Rajendra]

Hi Team,

We have precompileJSPs tests that include compilation of around 4000 jsp files. 
After upgrading to Tomcat 8.5.34 from Tomcat 8.5.32 we are facing an Error: 
java.lang.OutOfMemoryError: unable to create new native thread

The machines on which tests were executed have 16GB of RAM, out of which around 
13GB was free.
The precompileJSPs tests were executed on Tomcat 8.5.34 by setting ANT_OPTS 
from -Xmx4096m to -Xmx10240m, But Still the result was OutOfMemoryError.

However, We successfully tested precompileJSPs tests for Tomcat 8.5.32 with 
ANT_OPTS as -Xmx384m

Can someone please have a look into this issue?


Thanks and Regards,
Rajendra Rathore
9922701491

  
  


  



  

  





!+! EXITING FROM ANTCALL WITHIN PreCompileJsps[preCompileJsps.xml]

 [echo] FAILED to compile temp.jsp
 [echo] 
 [echo] The following error occurred while executing this line:
 [echo] preCompileJsps.xml: The following error occurred while executing 
this line:
 [echo] preCompileJsps.xml: java.lang.OutOfMemoryError: unable to create 
new native thread
  [antcall] Exiting preCompileJsps.xml.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: precompile JSPs failure issue - Tomcat community

[Rathore, Rajendra]

Hi Mark,

I am suspecting the same in 8.5.33 tomcat, do you still won't me to check it on 
tomcat 8.5.33?

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Guang Chao  
Sent: 01 November 2018 03:41 PM
To: Tomcat Users List 
Subject: Re: precompile JSPs failure issue - Tomcat community

On Thu, Nov 1, 2018 at 5:33 PM Mark Thomas  wrote:

> On 01/11/2018 09:21, Rathore, Rajendra wrote:
> > Hi Team,
> >
> >
> >
> > We have precompileJSPs tests that include compilation of around 4000 
> > jsp files. After upgrading to Tomcat *8.5.34* from Tomcat *8.5.32* 
> > we are facing an *Error:*/java.lang.OutOfMemoryError: unable to 
> > create new native thread /
> >
> >
> >
> > The machines on which tests were executed have *16GB* of RAM, out of 
> > which around *13GB* was free.
> >
> > The precompileJSPs tests were executed on Tomcat *8.5.34* by setting 
> > ANT_OPTS from -Xmx4096m to -Xmx10240m, But Still the result was 
> > /OutOfMemoryError./
> >
> > / /
> >
> > However, We successfully tested precompileJSPs tests for Tomcat 
> > *8.5.32 *with ANT_OPTS as -Xmx384m
> >
> >
> >
> > Can someone please have a look into this issue?
>
> Have you looked at the change log for the changes between 8.5.32 and
> 8.5.34 that might be relevant?
>

It could be changelog in 8.5.33
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.apache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D53011data=02%7C01%7Crarathore%40ptc.com%7Cb925903f163440c0623908d63fe25fc4%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C636766638847501834sdata=0pWCHhvlD%2FBKThN%2FvGEbfDE1%2F4SSXHYOaQIx028%2Fk9Q%3Dreserved=0
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.apache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D53492data=02%7C01%7Crarathore%40ptc.com%7Cb925903f163440c0623908d63fe25fc4%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C636766638847501834sdata=jzH4WEv0RTY%2BvJYmGvNIKS%2FFM6OSO4Kc8ZFRX4hmt2s%3Dreserved=0



>
> Have you tried testing with 8.5.33 to narrow down the version in which 
> the issue first appears?
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

--
Guang 
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjavadevnotes.com%2Fjava-string-to-datedata=02%7C01%7Crarathore%40ptc.com%7Cb925903f163440c0623908d63fe25fc4%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C636766638847501834sdata=S2z9J%2Bb75VYOsUR0aeRgyXIAjBTUVPvMxM7BU%2FGCDQ0%3Dreserved=0>

RE: precompile JSPs failure issue - Tomcat community

[Rathore, Rajendra]

Hi Chao,

We already tried it and it still failing.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Guang Chao  
Sent: 01 November 2018 06:07 PM
To: Tomcat Users List 
Subject: Re: precompile JSPs failure issue - Tomcat community

On Thu, Nov 1, 2018 at 7:13 PM Rathore, Rajendra  wrote:

> Hi Mark,
>
> I am suspecting the same in 8.5.33 tomcat, do you still won't me to 
> check it on tomcat 8.5.33?
>

How about increasing your perm memory?


>
> Thanks and Regards,
> Rajendra Rathore
> 9922701491
>
> -Original Message-
> From: Guang Chao 
> Sent: 01 November 2018 03:41 PM
> To: Tomcat Users List 
> Subject: Re: precompile JSPs failure issue - Tomcat community
>
> On Thu, Nov 1, 2018 at 5:33 PM Mark Thomas  wrote:
>
> > On 01/11/2018 09:21, Rathore, Rajendra wrote:
> > > Hi Team,
> > >
> > >
> > >
> > > We have precompileJSPs tests that include compilation of around 
> > > 4000 jsp files. After upgrading to Tomcat *8.5.34* from Tomcat 
> > > *8.5.32* we are facing an *Error:*/java.lang.OutOfMemoryError: 
> > > unable to create new native thread /
> > >
> > >
> > >
> > > The machines on which tests were executed have *16GB* of RAM, out 
> > > of which around *13GB* was free.
> > >
> > > The precompileJSPs tests were executed on Tomcat *8.5.34* by 
> > > setting ANT_OPTS from -Xmx4096m to -Xmx10240m, But Still the 
> > > result was /OutOfMemoryError./
> > >
> > > / /
> > >
> > > However, We successfully tested precompileJSPs tests for Tomcat
> > > *8.5.32 *with ANT_OPTS as -Xmx384m
> > >
> > >
> > >
> > > Can someone please have a look into this issue?
> >
> > Have you looked at the change log for the changes between 8.5.32 and
> > 8.5.34 that might be relevant?
> >
>
> It could be changelog in 8.5.33
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.ap
> ache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D53011data=02%7C01%7Crar
> athore%40ptc.com%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0d
> 828acb3381f678e2%7C0%7C0%7C636766727188877636sdata=diEmx1WNaWPvH%
> 2FGMd8Ex%2B4AgZCaGxcC6fez5UD%2FEF1c%3Dreserved=0
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.ap
> ache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D53492data=02%7C01%7Crar
> athore%40ptc.com%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0d
> 828acb3381f678e2%7C0%7C0%7C636766727188877636sdata=rl1N7m5upe4E7A
> 3zTAx4oht2cjUHfuDoNCWoOHKfkrs%3Dreserved=0
>
>
>
> >
> > Have you tried testing with 8.5.33 to narrow down the version in 
> > which the issue first appears?
> >
> > Mark
> >
> > 
> > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> >
>
> --
> Guang <
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjavade
> vnotes.com%2Fjava-string-to-datedata=02%7C01%7Crarathore%40ptc.co
> m%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0d828acb3381f678e
> 2%7C0%7C0%7C636766727188877636sdata=lEQmu2kFIquRsA5rAeVw17HYosy6O
> 03GGZvt6d6CWCA%3Dreserved=0
> >
>


--
Guang 
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjavadevnotes.com%2Fjava-string-comparedata=02%7C01%7Crarathore%40ptc.com%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C636766727188877636sdata=Cp43ZHDMP7TAF44aMFpRhyHSgN6qtRD7YnSHYiRUc%2FA%3Dreserved=0>

RE: precompile JSPs failure issue - Tomcat community

[Rathore, Rajendra]

Hi Rainer,

We never face this issue with tomcat 8.5.32 and from 8.5.33 it will causing the 
issue and it happen on both OS Window and Linux, it will be blocking for us 
because we are not able to update tomcat to latest on and it had some security 
issue fixed in it, please let me know how should I proceed from here.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rainer Jung  
Sent: 02 November 2018 03:50 PM
To: Tomcat Users List ; Rathore, Rajendra 

Subject: Re: precompile JSPs failure issue - Tomcat community

Am 02.11.2018 um 10:57 schrieb Rathore, Rajendra:
> Hi Mark,
> 
> I tried with tomcat 8.5.33 and face the same issue, I logged a bug 
> also
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.ap
> ache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D62879data=02%7C01%7Crar
> athore%40ptc.com%7C80d42185b225483c061508d640accfbb%7Cb9921086ff774d0d
> 828acb3381f678e2%7C0%7C0%7C636767508304565081sdata=FGguJAuq0y%2Ft
> TMNTsd%2Fezc6yTbuOD5wxzlNWdYs8wFI%3Dreserved=0
> 
> Please let me know how should I proceed here?
> 
> Thanks and Regards,
> Rajendra Rathore
> 9922701491
> 
> -Original Message-
> From: Rathore, Rajendra 
> Sent: 01 November 2018 06:10 PM
> To: Tomcat Users List 
> Subject: RE: precompile JSPs failure issue - Tomcat community
> 
> Hi Chao,
> 
> We already tried it and it still failing.
> 
> Thanks and Regards,
> Rajendra Rathore
> 9922701491
> 
> -Original Message-
> From: Guang Chao 
> Sent: 01 November 2018 06:07 PM
> To: Tomcat Users List 
> Subject: Re: precompile JSPs failure issue - Tomcat community
> 
> On Thu, Nov 1, 2018 at 7:13 PM Rathore, Rajendra  wrote:
> 
>> Hi Mark,
>>
>> I am suspecting the same in 8.5.33 tomcat, do you still won't me to 
>> check it on tomcat 8.5.33?
>>
> 
> How about increasing your perm memory?
> 
> 
>>
>> Thanks and Regards,
>> Rajendra Rathore
>> 9922701491
>>
>> -Original Message-
>> From: Guang Chao 
>> Sent: 01 November 2018 03:41 PM
>> To: Tomcat Users List 
>> Subject: Re: precompile JSPs failure issue - Tomcat community
>>
>> On Thu, Nov 1, 2018 at 5:33 PM Mark Thomas  wrote:
>>
>>> On 01/11/2018 09:21, Rathore, Rajendra wrote:
>>>> Hi Team,
>>>>
>>>>
>>>>
>>>> We have precompileJSPs tests that include compilation of around
>>>> 4000 jsp files. After upgrading to Tomcat *8.5.34* from Tomcat
>>>> *8.5.32* we are facing an *Error:*/java.lang.OutOfMemoryError:
>>>> unable to create new native thread /
>>>>
>>>>
>>>>
>>>> The machines on which tests were executed have *16GB* of RAM, out 
>>>> of which around *13GB* was free.
>>>>
>>>> The precompileJSPs tests were executed on Tomcat *8.5.34* by 
>>>> setting ANT_OPTS from -Xmx4096m to -Xmx10240m, But Still the result 
>>>> was /OutOfMemoryError./
>>>>
>>>> / /
>>>>
>>>> However, We successfully tested precompileJSPs tests for Tomcat
>>>> *8.5.32 *with ANT_OPTS as -Xmx384m
>>>>
>>>>
>>>>
>>>> Can someone please have a look into this issue?
>>>
>>> Have you looked at the change log for the changes between 8.5.32 and
>>> 8.5.34 that might be relevant?
>>>
>>
>> It could be changelog in 8.5.33
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.a
>> p 
>> ache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D53011data=02%7C01%7Cra
>> r 
>> athore%40ptc.com%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0
>> d 
>> 828acb3381f678e2%7C0%7C0%7C636766727188877636sdata=diEmx1WNaWPvH
>> %
>> 2FGMd8Ex%2B4AgZCaGxcC6fez5UD%2FEF1c%3Dreserved=0
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.a
>> p 
>> ache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D53492data=02%7C01%7Cra
>> r 
>> athore%40ptc.com%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0
>> d 
>> 828acb3381f678e2%7C0%7C0%7C636766727188877636sdata=rl1N7m5upe4E7
>> A
>> 3zTAx4oht2cjUHfuDoNCWoOHKfkrs%3Dreserved=0
>>
>>
>>
>>>
>>> Have you tried testing with 8.5.33 to narrow down the version in 
>>> which the issue first appears?
>>>
>>> Mark
>>>
>>> 
>>> - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org

RE: precompile JSPs failure issue - Tomcat community

[Rathore, Rajendra]

Hi Mark,

I tried with tomcat 8.5.33 and face the same issue, I logged a bug also
https://bz.apache.org/bugzilla/show_bug.cgi?id=62879

Please let me know how should I proceed here?

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rathore, Rajendra  
Sent: 01 November 2018 06:10 PM
To: Tomcat Users List 
Subject: RE: precompile JSPs failure issue - Tomcat community

Hi Chao,

We already tried it and it still failing.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Guang Chao 
Sent: 01 November 2018 06:07 PM
To: Tomcat Users List 
Subject: Re: precompile JSPs failure issue - Tomcat community

On Thu, Nov 1, 2018 at 7:13 PM Rathore, Rajendra  wrote:

> Hi Mark,
>
> I am suspecting the same in 8.5.33 tomcat, do you still won't me to 
> check it on tomcat 8.5.33?
>

How about increasing your perm memory?


>
> Thanks and Regards,
> Rajendra Rathore
> 9922701491
>
> -Original Message-
> From: Guang Chao 
> Sent: 01 November 2018 03:41 PM
> To: Tomcat Users List 
> Subject: Re: precompile JSPs failure issue - Tomcat community
>
> On Thu, Nov 1, 2018 at 5:33 PM Mark Thomas  wrote:
>
> > On 01/11/2018 09:21, Rathore, Rajendra wrote:
> > > Hi Team,
> > >
> > >
> > >
> > > We have precompileJSPs tests that include compilation of around
> > > 4000 jsp files. After upgrading to Tomcat *8.5.34* from Tomcat
> > > *8.5.32* we are facing an *Error:*/java.lang.OutOfMemoryError: 
> > > unable to create new native thread /
> > >
> > >
> > >
> > > The machines on which tests were executed have *16GB* of RAM, out 
> > > of which around *13GB* was free.
> > >
> > > The precompileJSPs tests were executed on Tomcat *8.5.34* by 
> > > setting ANT_OPTS from -Xmx4096m to -Xmx10240m, But Still the 
> > > result was /OutOfMemoryError./
> > >
> > > / /
> > >
> > > However, We successfully tested precompileJSPs tests for Tomcat
> > > *8.5.32 *with ANT_OPTS as -Xmx384m
> > >
> > >
> > >
> > > Can someone please have a look into this issue?
> >
> > Have you looked at the change log for the changes between 8.5.32 and
> > 8.5.34 that might be relevant?
> >
>
> It could be changelog in 8.5.33
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.ap
> ache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D53011data=02%7C01%7Crar
> athore%40ptc.com%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0d
> 828acb3381f678e2%7C0%7C0%7C636766727188877636sdata=diEmx1WNaWPvH%
> 2FGMd8Ex%2B4AgZCaGxcC6fez5UD%2FEF1c%3Dreserved=0
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.ap
> ache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D53492data=02%7C01%7Crar
> athore%40ptc.com%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0d
> 828acb3381f678e2%7C0%7C0%7C636766727188877636sdata=rl1N7m5upe4E7A
> 3zTAx4oht2cjUHfuDoNCWoOHKfkrs%3Dreserved=0
>
>
>
> >
> > Have you tried testing with 8.5.33 to narrow down the version in 
> > which the issue first appears?
> >
> > Mark
> >
> > 
> > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> >
>
> --
> Guang <
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjavade
> vnotes.com%2Fjava-string-to-datedata=02%7C01%7Crarathore%40ptc.co
> m%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0d828acb3381f678e
> 2%7C0%7C0%7C636766727188877636sdata=lEQmu2kFIquRsA5rAeVw17HYosy6O
> 03GGZvt6d6CWCA%3Dreserved=0
> >
>


--
Guang 
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjavadevnotes.com%2Fjava-string-comparedata=02%7C01%7Crarathore%40ptc.com%7Ce055c122a344402f19ff08d63ff74502%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C636766728579713014sdata=wcK%2FUGcxwfCAgJVNS4TvabtLLsGavYUKrEON1uDUpCQ%3Dreserved=0>
B CB  [  
X  ܚX KK[XZ[
 \ \  ][  X  ܚX P X ]
 \X K ܙ B  ܈Y][ۘ[  [X[  K[XZ[
 \ \  Z[ X ]
 \X K ܙ B 

RE: precompile JSPs failure issue - Tomcat community

[Rathore, Rajendra]

Hi Rainer/Chris,

I tried below command, it also fails with same error,
Please find attached output of strace command, I am unable to found any help 
from that file or I might not have much idea about it, can you please check it 
and let me know your finding, mean while is there any way to run the jspc 
command in single thread model like 8.5.32 tomcat version.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Christopher Schultz  
Sent: 02 November 2018 06:48 PM
To: users@tomcat.apache.org
Subject: Re: precompile JSPs failure issue - Tomcat community

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Rainer,

On 11/2/18 06:20, Rainer Jung wrote:
> You can control the number of threads using -threadCount. By default 
> the number is equals to the number of cores the operating system show 
> to the JVM.

x 2

> You might want to use a smaller number to see whether that helps.
> 
> I suggest you also check your Linux system limits on processes per 
> user. That system limit on Linux in fact limits threads per user.
> So if such a limit is set and your user has other processes with many 
> threads running, you might need to increase this limit.
> 
> In addition you can run your ant process with
> 
> strace -f -o /var/tmp/strace.out HERE_COMES_YOUR_ANT_COMMAND &
> 
> Then after you get the error, you can check the strace.out file for 
> system call errors. The file will be big, but most probably the error 
> is relatively close to the end.

- -chris

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

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlvcTpgACgkQHPApP6U8
pFjorRAAgGTY4qhWtokCdEqowTjN3rWQUk75aCCEEX/zxhQloiXf3cC1CeQEDqjG
SwnATFP7VN7/z1vAdgV9MQlK4SFBy5mp/Tf8HL8K33h6kv0CoEIcvjYbn5fUbpAu
QxmD7zZzEol2hXaKm8+oMnIe28G+dp74jqEpUgbhLDZhd4gAZxc+lejkHRIM8Sqj
hAdi1jh3cslwRpHf5j+Ff9BvYfAuS7ET6aT6e85zsFotj3S6LoXr8zX2HxoDuYWc
P1OebWr9lrJDp/QZEdVDGYPk3b4mZWWG56BK0TTBo+b0TY+52bgXnG71g0tfK1PB
MV1E4wVOj1wYwTuqmZIBXUfLzvGZMIEDG8p4Ne/pM3Hf/ekViQdW7wE19Ro28b3m
iF5AQqeG80P+yerTk7Vic5p7YV11rZrnFT9bUYOe3zBwLJL/GG9zgBQJj1usGtLT
nCmS/7wj4YvqWr8UtagqfbzYyXpEZZ0ZQt67bfONLCXTyyDkd4vRQauGJkMnQEL3
Qobw9SVOefxvVa7ChNBmja6KlmsGhmSlSzW51o2UUiGuwl0tuuwuccw4A+baUMF+
8d/rfzEhFW7SF4Y1/681rvWoEyxA05ILd80+i9BSzr66z+v2+21i5ivWqYZ+TWaF
g8X7kk84JriPgiEbuwqvCG6TmpaXOF0w1FW20s28XiH7uvyllPE=
=/xUp
-END PGP SIGNATURE-

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

10807 stat("/utf/target/Windchill/codebase/wtcore/test/dynAnon.jsp", 
{st_mode=S_IFREG|0775, st_size=360, ...}) = 0
10807 clone(child_stack=0x7f53af001fb0, 
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
 parent_tidptr=0x7f53af0029d0, tls=0x7f53af002700, child_tidptr=0x7f53af0029d0) 
= -1 EAGAIN (Resource temporarily unavailable)
10807 write(1, "!+! ERROR OCCURRED @ /utf/target"..., 81) = 81
10807 write(1, "\n", 1) = 1
10807 write(36, "!+! ERROR OCCURRED @ /utf/target"..., 81) = 81
10807 write(36, "\n", 1)= 1
10807 write(1, "  [antcall] Exiting /utf/target/"..., 71) = 71
10807 write(1, "\n", 1) = 1
10807 write(36, "  [antcall] Exiting /utf/target/"..., 71) = 71
10807 write(36, "\n", 1)= 1
10807 write(1, "\n---"..., 261) = 261
10807 write(1, "\n", 1) = 1
10807 write(36, "\n---"..., 261) = 261
10807 write(36, "\n", 1)= 1
10807 write(1, "!+! ERROR OCCURRED @ /utf/target"..., 81) = 81
10807 write(1, "\n", 1) = 1
10807 write(36, "!+! ERROR OCCURRED @ /utf/target"..., 81) = 81
10807 write(36, "\n", 1)= 1
10807 write(1, "  [antcall] Exiting /utf/target/"..., 71) = 71
10807 write(1, "\n", 1) = 1
10807 write(36, "  [antcall] Exiting /utf/target/"..., 71) = 71
10807 write(36, "\n", 1)= 1
10807 write(1, "\n---"..., 261) = 261
10807 write(1, "\n", 1) = 1
10807 write(36, "\n---"..., 261) = 261
10807 write(36, "\n", 1)= 1
10807 write(1, " [echo] FAILED to compile wt"..., 53) = 53
10807 write(1, "\n", 1) = 1
10807 write(36, " [echo] FAILED to compile wt"..., 53) = 53
10807 write(36, "\n", 1)= 1
10807 write(1, " [echo] ", 12)  = 12
10807 write(1, "\n", 1) = 1
10807 write(36, " [echo] ", 12) = 12
10807 write(36, "\n", 1)= 1
10807 write(1, " [echo] The following error "..., 67) = 67
10807 write(1, "\n", 1) = 1
10807 write(36, " [echo] The following error "..., 67) = 67
10807 write(36, "\n", 1)= 1
10807 write(1, " [echo] /utf/target/Windchil"..., 123) = 123
10807 

RE: loss of connection with mod_jk(tomcat connector)

[Rathore, Rajendra]

Hi Mark,

We configure multiple tomcat and based on the configuration start other tomcat, 
since one tomcat running fine but after some time it will stop communicating, 
this problem we face from Tomcat Connector 1.2.46 version onwards, for 1.2.43 
it works fine, please let me know if I need to enable extra loggers that will 
help out to understand the problem better,

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Mark Thomas  
Sent: 17 January 2019 05:05 AM
To: Tomcat Users List 
Subject: Re: loss of connection with mod_jk(tomcat connector)

External email from: users-return-29-rarathore=ptc@tomcat.apache.org

On 16/01/2019 12:26, Rathore, Rajendra wrote:
> Hi Team,
> 
>  
> 
> we are using Apache Http server with basic authentication, when we try 
> to send some request to apache for authentication it will fail with 
> 401 error and when we check the JK Status,
> 
> we found that status was not proper means instead of 'OK' state it was 
> 'Awaiting..'. We are facing this issue with tomcat connector 1.2.46, 
> it worked with 1.2.43. I attached our log files for your reference, 
> please let me know if you need anything else.

Logs show the Tomcat instances aren't listening on the configured host/ports.

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: loss of connection with mod_jk(tomcat connector)

[Rathore, Rajendra]

Hi Rainer,

I am not much aware about JkShmFile but it was working fine with tomcat 
connector 1.2.43, is anything I need to setup for more loggers because even I 
am also not getting the actual problem.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rainer Jung  
Sent: 06 February 2019 06:41 PM
To: Tomcat Users List ; Rathore, Rajendra 

Subject: Re: loss of connection with mod_jk(tomcat connector)

External email from: rainer.j...@kippdata.de

Hi Rajendra,

Am 06.02.2019 um 12:36 schrieb Rathore, Rajendra:
> Hi Mark,
> 
> I am stuck and due to below issue unable to update to latest tomcat 
> connector, can you please share your finding, let me know if you need 
> anything from my side, I also raise issue 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.apache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D63075data=02%7C01%7Crarathore%40ptc.com%7C1a09aaa2eae847b573eb08d68c349039%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C636850554720305577sdata=6u4FOXO5xbYRAJ2GFXE8zwNOIZ2MyNuVtuphdD6xur0%3Dreserved=0
>  but there is no progress on it.

as Mark already wrote, your mod_jk log file shows, that many of your tomcat 
instances are down.

You have configured a load balancer with 9 members, listening on localhost 
ports 8010-8018, but of these 9 tomcat instances only the one listening on port 
8010 was up. So some requests work, because they were forwarded coincidentally 
to the working port, others fail, because they were forwarded to one of the 8 
ports were nothing is listening and even their failover failed, because when 
only one out of 9 ports work, chances are very high, that the failover also 
hits a port where nothing listens.

mod_jk remembers the failing workers (ports) for some time and will not retry 
to use them, but as I wrote in the ticket, you have a broken JkShmFile, so 
mod_jk balancers can not correctly work. Fix that problem first and make sure 
your ports are actually listening.

Regards,

Rainer

> -Original Message-
> From: Rathore, Rajendra 
> Sent: 17 January 2019 10:33 AM
> To: Tomcat Users List 
> Subject: RE: loss of connection with mod_jk(tomcat connector)
> 
> External email from: 
> users-return-266670-rarathore=ptc@tomcat.apache.org
> 
> Hi Mark,
> 
> We configure multiple tomcat and based on the configuration start 
> other tomcat, since one tomcat running fine but after some time it 
> will stop communicating, this problem we face from Tomcat Connector 
> 1.2.46 version onwards, for 1.2.43 it works fine, please let me know 
> if I need to enable extra loggers that will help out to understand the 
> problem better,
> 
> Thanks and Regards,
> Rajendra Rathore
> 9922701491
> 
> -Original Message-
> From: Mark Thomas 
> Sent: 17 January 2019 05:05 AM
> To: Tomcat Users List 
> Subject: Re: loss of connection with mod_jk(tomcat connector)
> 
> External email from: 
> users-return-29-rarathore=ptc@tomcat.apache.org
> 
> On 16/01/2019 12:26, Rathore, Rajendra wrote:
>> Hi Team,
>>
>>   
>>
>> we are using Apache Http server with basic authentication, when we 
>> try to send some request to apache for authentication it will fail 
>> with
>> 401 error and when we check the JK Status,
>>
>> we found that status was not proper means instead of 'OK' state it 
>> was 'Awaiting..'. We are facing this issue with tomcat connector 
>> 1.2.46, it worked with 1.2.43. I attached our log files for your 
>> reference, please let me know if you need anything else.
> 
> Logs show the Tomcat instances aren't listening on the configured host/ports.
> 
> Mark

RE: loss of connection with mod_jk(tomcat connector)

[Rathore, Rajendra]

Hi Mark,

I am stuck and due to below issue unable to update to latest tomcat connector, 
can you please share your finding, let me know if you need anything from my 
side, I also raise issue https://bz.apache.org/bugzilla/show_bug.cgi?id=63075 
but there is no progress on it.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rathore, Rajendra  
Sent: 17 January 2019 10:33 AM
To: Tomcat Users List 
Subject: RE: loss of connection with mod_jk(tomcat connector)

External email from: users-return-266670-rarathore=ptc@tomcat.apache.org

Hi Mark,

We configure multiple tomcat and based on the configuration start other tomcat, 
since one tomcat running fine but after some time it will stop communicating, 
this problem we face from Tomcat Connector 1.2.46 version onwards, for 1.2.43 
it works fine, please let me know if I need to enable extra loggers that will 
help out to understand the problem better,

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Mark Thomas 
Sent: 17 January 2019 05:05 AM
To: Tomcat Users List 
Subject: Re: loss of connection with mod_jk(tomcat connector)

External email from: users-return-29-rarathore=ptc@tomcat.apache.org

On 16/01/2019 12:26, Rathore, Rajendra wrote:
> Hi Team,
> 
>  
> 
> we are using Apache Http server with basic authentication, when we try 
> to send some request to apache for authentication it will fail with
> 401 error and when we check the JK Status,
> 
> we found that status was not proper means instead of 'OK' state it was 
> 'Awaiting..'. We are facing this issue with tomcat connector 1.2.46, 
> it worked with 1.2.43. I attached our log files for your reference, 
> please let me know if you need anything else.

Logs show the Tomcat instances aren't listening on the configured host/ports.

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

issue faced in tomcat 8.5.51

[Rathore, Rajendra]

Hi Team,

I am using below configuration in server.xml for tomcat



but I got below exception in start up time

2020-02-27 17:59:57,524 ERROR [Servlet engine main] 
org.apache.catalina.core.StandardService  - Failed to start connector 
[Connector[AJP/1.3-8010]]
org.apache.catalina.LifecycleException: Protocol handler start failed
   at 
org.apache.catalina.connector.Connector.startInternal(Connector.java:1057)
   at 
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
   at 
org.apache.catalina.core.StandardService.startInternal(StandardService.java:440)
   at 
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
   at 
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:766)
   at 
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:688)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:498)
   at 
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:343)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:498)
   at com.ptc.tomcat.embedded.Bootstrap.start(Bootstrap.java:495)
   at com.ptc.tomcat.embedded.Bootstrap.start(Bootstrap.java:439)
   at 
com.ptc.tomcat.embedded.Bootstrap.lambda$new$0(Bootstrap.java:167)
   at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: The AJP Connector is configured 
with secretRequired="true" but the secret attribute is either null or "". This 
combination is not valid.
   at 
org.apache.coyote.ajp.AbstractAjpProtocol.start(AbstractAjpProtocol.java:274)
   at 
org.apache.catalina.connector.Connector.startInternal(Connector.java:1055)
   ... 19 more


Please let me know what should I put to fix the issue, it will be very helpful 
for me.

I am stuck because of the above issue, we are using Apache and tomcat for 
serving the request.

Let me know if anything else required from my side.


Thanks and Regards,
Rajendra Rathore
9922701491

RE: issue faced in tomcat 8.5.51

[Rathore, Rajendra]

Hi Calder/Team,

I set the below flag as false but still it will giving the same error.

I am using Apache http server(with AJP worker) and tomcat configuration, Is am 
I missing something in configuration, please let me know?

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: calder  
Sent: Friday, February 28, 2020 7:41 PM
To: Tomcat Users List 
Subject: Re: issue faced in tomcat 8.5.51

External email from: users-return-269823-rarathore=ptc@tomcat.apache.org

On Fri, Feb 28, 2020, 07:39 Rathore, Rajendra  wrote:

> Hi Team,
>
> I am using below configuration in server.xml for tomcat
>
>  secretRequired="false" secure="false"  address="127.0.0.1"
>tomcatAuthentication="false" enableLookups="false"
> maxPostSize="-1" maxSavePostSize="8388608" maxParameterCount="-1"
>useBodyEncodingForURI="true" URIEncoding="UTF-8"
> backlog="100" packetSize="8192"
>maxThreads="320" minSpareThreads="8"/>
>
> but I got below exception in start up time
>

< snip >

>

Caused by: java.lang.IllegalArgumentException:

The AJP Connector is configured with secretRequired="true" but the secret
> attribute is either null or "". This combination is not valid
>





Please let me know what should I put to fix the issue, it will be very
> helpful for me.
>
> I am stuck because of the above issue, we are using Apache and tomcat 
> for serving the request.
>
> Let me know if anything else required from my side.
>

RE: BLOCKING: performance issue with Tomcat 8.5.35 in org.apache.tomcat.util.net.NioBlockingSelector.write API

[Rathore, Rajendra]

Hi Team,

If someone know how to check whether proper read/write operation done or not or 
it will caused by network please let me know because it is blocking for me.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rathore, Rajendra 
Sent: Wednesday, January 8, 2020 11:43 AM
To: 'Tomcat Users List' 
Subject: RE: performance issue with Tomcat 8.5.35 in 
org.apache.tomcat.util.net.NioBlockingSelector.write API

Can someone please help me to find out the root cause for below issue.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rathore, Rajendra
Sent: Tuesday, January 7, 2020 4:16 PM
To: Tomcat Users List 
Subject: RE: performance issue with Tomcat 8.5.35 in 
org.apache.tomcat.util.net.NioBlockingSelector.write API

Hi Remy,

Thanks for the reply,

As you mention below points

"There's a problem only if things are blocked improperly, for example if the 
client is correctly reading the data and/or there's no network backlog.
Also the timeout configured on the connector must be respected by the 
operation."

1. how can we check the network backlog or data read/write not working 
properly, if any tool pls let us know 2. how can we set connector timeout.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rémy Maucherat 
Sent: Tuesday, January 7, 2020 4:11 PM
To: Tomcat Users List 
Subject: Re: performance issue with Tomcat 8.5.35 in 
org.apache.tomcat.util.net.NioBlockingSelector.write API

External email from: users-return-269207-rarathore=ptc@tomcat.apache.org

On Tue, Jan 7, 2020 at 6:33 AM Rathore, Rajendra  wrote:

> Hi Rémy/ Christopher,
>
> It will stuck there for 10-15 minutes, so it will take time to load 
> simple Web UI, there is no WebSocket call. I am giving you one of the 
> sample where it will take 90% time in write operation, sometime it will reach 
> to 100%.
>
>
>  ||
>
> O-org.apache.coyote.ajp.AjpProcessor.writeData(AjpProcessor.java:1331)
> count=1669(%92.877)
>  ||
>   
> O-org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBase
> .java:385)
> count=1669(%92.877)
>  ||
> 
> O-org.apache.tomcat.util.net.SocketWrapperBase.writeBlocking(SocketWra
> pperBase.java:462)
> count=1669(%92.877)
>  ||
>   
> O-org.apache.tomcat.util.net.SocketWrapperBase.doWrite(SocketWrapperBa
> se.java:726)
> count=1669(%92.877)
>  ||
> 
> O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doWrite(NioE
> ndpoint.java:1316)
> count=1669(%92.877)
>  ||
>   
> O-org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.jav
> a:157)
> count=1669(%92.877)
>  ||
> 
> O-org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSele
> ctor.java:114)
> count=1667(%92.766)
>  ||
> |
> O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.awaitWriteLa
> tch(NioEndpoint.java:1160)
> count=1667(%92.766)
>  ||
> |
> O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.awaitLatch(NioEndpoint.java:1157)
> count=1667(%92.766)
>  ||
> |
> O-java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
> count=1667(%92.766)
>
>
It's a normal blocking write, and the await does not consume CPU (it sits there 
however and a profiler will count that but it doesn't matter).
There's a problem only if things are blocked improperly, for example if the 
client is correctly reading the data and/or there's no network backlog.
Also the timeout configured on the connector must be respected by the operation.

Rémy

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

RE: BLOCKING: performance issue with Tomcat 8.5.35 in org.apache.tomcat.util.net.NioBlockingSelector.write API

[Rathore, Rajendra]

Hi Zahid,

How below link is going to help me out to know the root cause of the problem?

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Zahid Rahman  
Sent: Thursday, January 9, 2020 10:53 AM
To: Tomcat Users List 
Subject: Re: BLOCKING: performance issue with Tomcat 8.5.35 in 
org.apache.tomcat.util.net.NioBlockingSelector.write API

External email from: users-return-269283-rarathore=ptc@tomcat.apache.org

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.codota.com%2Fcode%2Fjava%2Fmethods%2Forg.apache.tomcat.util.net.NioBlockingSelector%2Fopendata=02%7C01%7Crarathore%40ptc.com%7C02a8c62f96c84b8ea63c08d794c40c25%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637141442053995621sdata=E666bJmF4N1wxBhm%2Fa%2BY29lvLlA32tQ%2B4F3lwBnLM2g%3Dreserved=0


On Thu, 9 Jan 2020, 04:49 Rathore, Rajendra,  wrote:

> Hi Team,
>
> If someone know how to check whether proper read/write operation done 
> or not or it will caused by network please let me know because it is 
> blocking for me.
>
> Thanks and Regards,
> Rajendra Rathore
> 9922701491
>
> -----Original Message-
> From: Rathore, Rajendra
> Sent: Wednesday, January 8, 2020 11:43 AM
> To: 'Tomcat Users List' 
> Subject: RE: performance issue with Tomcat 8.5.35 in 
> org.apache.tomcat.util.net.NioBlockingSelector.write API
>
> Can someone please help me to find out the root cause for below issue.
>
> Thanks and Regards,
> Rajendra Rathore
> 9922701491
>
> -Original Message-
> From: Rathore, Rajendra
> Sent: Tuesday, January 7, 2020 4:16 PM
> To: Tomcat Users List 
> Subject: RE: performance issue with Tomcat 8.5.35 in 
> org.apache.tomcat.util.net.NioBlockingSelector.write API
>
> Hi Remy,
>
> Thanks for the reply,
>
> As you mention below points
>
> "There's a problem only if things are blocked improperly, for example 
> if the client is correctly reading the data and/or there's no network backlog.
> Also the timeout configured on the connector must be respected by the 
> operation."
>
> 1. how can we check the network backlog or data read/write not working 
> properly, if any tool pls let us know 2. how can we set connector timeout.
>
> Thanks and Regards,
> Rajendra Rathore
> 9922701491
>
> -Original Message-
> From: Rémy Maucherat 
> Sent: Tuesday, January 7, 2020 4:11 PM
> To: Tomcat Users List 
> Subject: Re: performance issue with Tomcat 8.5.35 in 
> org.apache.tomcat.util.net.NioBlockingSelector.write API
>
> External email from: users-return-269207-rarathore= 
> ptc@tomcat.apache.org
>
> On Tue, Jan 7, 2020 at 6:33 AM Rathore, Rajendra 
> wrote:
>
> > Hi Rémy/ Christopher,
> >
> > It will stuck there for 10-15 minutes, so it will take time to load 
> > simple Web UI, there is no WebSocket call. I am giving you one of 
> > the sample where it will take 90% time in write operation, sometime 
> > it will
> reach to 100%.
> >
> >
> >  ||
> >
> > O-org.apache.coyote.ajp.AjpProcessor.writeData(AjpProcessor.java:133
> > 1)
> > count=1669(%92.877)
> >  ||
> >
> > O-org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBa
> > se
> > .java:385)
> > count=1669(%92.877)
> >  ||
> >
> > O-org.apache.tomcat.util.net.SocketWrapperBase.writeBlocking(SocketW
> > ra
> > pperBase.java:462)
> > count=1669(%92.877)
> >  ||
> >
> > O-org.apache.tomcat.util.net.SocketWrapperBase.doWrite(SocketWrapper
> > Ba
> > se.java:726)
> > count=1669(%92.877)
> >  ||
> >
> > O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doWrite(Ni
> > oE
> > ndpoint.java:1316)
> > count=1669(%92.877)
> >  ||
> >
> > O-org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.j
> > av
> > a:157)
> > count=1669(%92.877)
> >  ||
> >
> > O-org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSe
> > le
> > ctor.java:114)
> > count=1667(%92.766)
> >  ||
> > |
> > O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.awaitWrite
> > La
> > tch(NioEndpoint.java:1160)
> >

performance issue with Tomcat 8.5.35 in org.apache.tomcat.util.net.NioBlockingSelector.write API

[Rathore, Rajendra]

Hi Team,

We are facing performance issue during 
org.apache.tomcat.util.net.NioBlockingSelector.write API call, ,most of our 
thread stuck and spending more time in that API, you can check below screenshot 
for more details.


[cid:image002.jpg@01D5C4BA.A1BBFAB0]


We debug the code and found that NioChannel.write method return 0(Zero) value, 
in that case our threads are stuck, Please  let us know why this happen.

Please let me know if you need more details.


Thanks and Regards,
Rajendra Rathore
9922701491

RE: performance issue with Tomcat 8.5.35 in org.apache.tomcat.util.net.NioBlockingSelector.write API

[Rathore, Rajendra]

-org.apache.coyote.ajp.AjpProcessor.writeData(AjpProcessor.java:1331) 
count=1669(%92.877)
 || 
 
O-org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBase.java:385)
 count=1669(%92.877)
 || 
   
O-org.apache.tomcat.util.net.SocketWrapperBase.writeBlocking(SocketWrapperBase.java:462)
 count=1669(%92.877)
 || 
 
O-org.apache.tomcat.util.net.SocketWrapperBase.doWrite(SocketWrapperBase.java:726)
 count=1669(%92.877)
 || 
   
O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doWrite(NioEndpoint.java:1316)
 count=1669(%92.877)
 || 
 
O-org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.java:157) 
count=1669(%92.877)
 || 
   
O-org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSelector.java:114)
 count=1667(%92.766)
 || 
   |  
O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.awaitWriteLatch(NioEndpoint.java:1160)
 count=1667(%92.766)
 || 
   |
O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.awaitLatch(NioEndpoint.java:1157)
 count=1667(%92.766)
 || 
   |  
O-java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) 
count=1667(%92.766)

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rémy Maucherat  
Sent: Monday, January 6, 2020 10:18 PM
To: Tomcat Users List 
Subject: Re: performance issue with Tomcat 8.5.35 in 
org.apache.tomcat.util.net.NioBlockingSelector.write API

External email from: users-return-269178-rarathore=ptc@tomcat.apache.org

On Mon, Jan 6, 2020 at 1:27 PM Rathore, Rajendra  wrote:

> Hi Team,
>
>
>
> We are facing performance issue during 
> *org.apache.tomcat.util.net.NioBlockingSelector.write
> API call, *,most of our thread stuck and spending more time in that 
> API, you can check below screenshot for more details.
>
>
>
>
>
>
>
>
>
> We debug the code and found that NioChannel.write method return 
> 0(Zero) value, in that case our threads are stuck, Please  let us know 
> why this happen.
>

As NIO is non blocking IO, 0 bytes written means there's a backlog and output 
will block in NioBlockingSelector since it emulates blocking IO there. It 
should not actually consume CPU, just wait until there's a poller event 
indicating writing data may continue.

Rémy


>
>
> Please let me know if you need more details.
>
>
>
>
>
> Thanks and Regards,
>
> Rajendra Rathore
>
> 9922701491
>
>
>

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

RE: performance issue with Tomcat 8.5.35 in org.apache.tomcat.util.net.NioBlockingSelector.write API

[Rathore, Rajendra]

Hi Remy,

Thanks for the reply,

As you mention below points

"There's a problem only if things are blocked improperly, for example if the 
client is correctly reading the data and/or there's no network backlog.
Also the timeout configured on the connector must be respected by the 
operation."

1. how can we check the network backlog or data read/write not working 
properly, if any tool pls let us know
2. how can we set connector timeout.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rémy Maucherat  
Sent: Tuesday, January 7, 2020 4:11 PM
To: Tomcat Users List 
Subject: Re: performance issue with Tomcat 8.5.35 in 
org.apache.tomcat.util.net.NioBlockingSelector.write API

External email from: users-return-269207-rarathore=ptc@tomcat.apache.org

On Tue, Jan 7, 2020 at 6:33 AM Rathore, Rajendra  wrote:

> Hi Rémy/ Christopher,
>
> It will stuck there for 10-15 minutes, so it will take time to load 
> simple Web UI, there is no WebSocket call. I am giving you one of the 
> sample where it will take 90% time in write operation, sometime it will reach 
> to 100%.
>
>
>  ||
>
> O-org.apache.coyote.ajp.AjpProcessor.writeData(AjpProcessor.java:1331)
> count=1669(%92.877)
>  ||
>   
> O-org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBase
> .java:385)
> count=1669(%92.877)
>  ||
> 
> O-org.apache.tomcat.util.net.SocketWrapperBase.writeBlocking(SocketWra
> pperBase.java:462)
> count=1669(%92.877)
>  ||
>   
> O-org.apache.tomcat.util.net.SocketWrapperBase.doWrite(SocketWrapperBa
> se.java:726)
> count=1669(%92.877)
>  ||
> 
> O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doWrite(NioE
> ndpoint.java:1316)
> count=1669(%92.877)
>  ||
>   
> O-org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.jav
> a:157)
> count=1669(%92.877)
>  ||
> 
> O-org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSele
> ctor.java:114)
> count=1667(%92.766)
>  ||
> |  
> O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.awaitWriteLa
> tch(NioEndpoint.java:1160)
> count=1667(%92.766)
>  ||
> |
> O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.awaitLatch(NioEndpoint.java:1157)
> count=1667(%92.766)
>  ||
> |
> O-java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
> count=1667(%92.766)
>
>
It's a normal blocking write, and the await does not consume CPU (it sits there 
however and a profiler will count that but it doesn't matter).
There's a problem only if things are blocked improperly, for example if the 
client is correctly reading the data and/or there's no network backlog.
Also the timeout configured on the connector must be respected by the operation.

Rémy

RE: performance issue with Tomcat 8.5.35 in org.apache.tomcat.util.net.NioBlockingSelector.write API

[Rathore, Rajendra]

Can someone please help me to find out the root cause for below issue.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rathore, Rajendra 
Sent: Tuesday, January 7, 2020 4:16 PM
To: Tomcat Users List 
Subject: RE: performance issue with Tomcat 8.5.35 in 
org.apache.tomcat.util.net.NioBlockingSelector.write API

Hi Remy,

Thanks for the reply,

As you mention below points

"There's a problem only if things are blocked improperly, for example if the 
client is correctly reading the data and/or there's no network backlog.
Also the timeout configured on the connector must be respected by the 
operation."

1. how can we check the network backlog or data read/write not working 
properly, if any tool pls let us know 2. how can we set connector timeout.

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rémy Maucherat 
Sent: Tuesday, January 7, 2020 4:11 PM
To: Tomcat Users List 
Subject: Re: performance issue with Tomcat 8.5.35 in 
org.apache.tomcat.util.net.NioBlockingSelector.write API

External email from: users-return-269207-rarathore=ptc@tomcat.apache.org

On Tue, Jan 7, 2020 at 6:33 AM Rathore, Rajendra  wrote:

> Hi Rémy/ Christopher,
>
> It will stuck there for 10-15 minutes, so it will take time to load 
> simple Web UI, there is no WebSocket call. I am giving you one of the 
> sample where it will take 90% time in write operation, sometime it will reach 
> to 100%.
>
>
>  ||
>
> O-org.apache.coyote.ajp.AjpProcessor.writeData(AjpProcessor.java:1331)
> count=1669(%92.877)
>  ||
>   
> O-org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBase
> .java:385)
> count=1669(%92.877)
>  ||
> 
> O-org.apache.tomcat.util.net.SocketWrapperBase.writeBlocking(SocketWra
> pperBase.java:462)
> count=1669(%92.877)
>  ||
>   
> O-org.apache.tomcat.util.net.SocketWrapperBase.doWrite(SocketWrapperBa
> se.java:726)
> count=1669(%92.877)
>  ||
> 
> O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doWrite(NioE
> ndpoint.java:1316)
> count=1669(%92.877)
>  ||
>   
> O-org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.jav
> a:157)
> count=1669(%92.877)
>  ||
> 
> O-org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSele
> ctor.java:114)
> count=1667(%92.766)
>  ||
> |
> O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.awaitWriteLa
> tch(NioEndpoint.java:1160)
> count=1667(%92.766)
>  ||
> |
> O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.awaitLatch(NioEndpoint.java:1157)
> count=1667(%92.766)
>  ||
> |
> O-java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
> count=1667(%92.766)
>
>
It's a normal blocking write, and the await does not consume CPU (it sits there 
however and a profiler will count that but it doesn't matter).
There's a problem only if things are blocked improperly, for example if the 
client is correctly reading the data and/or there's no network backlog.
Also the timeout configured on the connector must be respected by the operation.

Rémy

regarding CVE-2020-8022 applicable to tomcat 8.5.57

[Rathore, Rajendra]

Hi Team,

Please let me know whether CVE-2020-8022 applicable to tomcat 8.5.57 or not, if 
yes please let me know which release we fixing it.

Thanks and Regards,
Rajendra Rathore
9922701491

hiding tomcat version from error pages

[Rathore, Rajendra]

Hi All,

Please let me know the standard way to hide tomcat version from error pages, I 
tried on google and saying that you need to modify some properties inside 
catelina.jar, but that is not a standard way.

[cid:image003.jpg@01D68D1A.F310D100]

Thanks and Regards,
Rajendra Rathore
9922701491

RE: hiding tomcat version from error pages

[Rathore, Rajendra]

Hi Tim,

I am using tomcat 8.5.x, will that available over there?

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Tim Funk  
Sent: Thursday, September 17, 2020 6:12 PM
To: Tomcat Users List 
Subject: Re: hiding tomcat version from error pages

External email from: users-return-271678-rarathore=ptc@tomcat.apache.org

It should a tweak to the ErrorReportValve as documented here: (inside of
server.xml)

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftomcat.apache.org%2Ftomcat-9.0-doc%2Fconfig%2Fvalve.html%23Error_Report_Valvedata=02%7C01%7Crarathore%40ptc.com%7Cf025f80f3c7f4f94aadf08d85b074060%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C1%7C637359433989184801sdata=eMHYctj3jTQW5WSlAfbKXukvFuh7Jvnudb%2BO8s8%2BzCw%3Dreserved=0

You'll want to set showServerInfo and showReport to false

-Tim


On Thu, Sep 17, 2020 at 8:20 AM Rathore, Rajendra  wrote:

> Hi All,
>
>
>
> Please let me know the standard way to hide tomcat version from error 
> pages, I tried on google and saying that you need to modify some 
> properties inside catelina.jar, but that is not a standard way.
>
>
>
>
>
> Thanks and Regards,
>
> Rajendra Rathore
>
> 9922701491
>
>
>

issue with Form based authentication

[Rathore, Rajendra]

Hi Team,

We are facing some weird issue with tomcat Form based authentication, I will 
try to explain the scenario as below:

issue is reproducible in specific conditions, when browser cache is disabled, 
and cleared out before session timeout. In this conditions after session 
timeout when user is moving mouse over some elements where requests for GIFs 
are sent. Those request are processed by FormAuthenticator tomcat class. This 
class is responsible for saving requested URL and redirecting user to this 
saved URL after successful login. But this class saves in session all requests 
using the same key, this means that old requests are overrided by new ones. In 
this case there are multiple requests after session timeout, to get some GIFs, 
and to show relogin.jsp in popup window, those requests are handled by 
different threads, and last executed thread is saving to session information 
about requested URL. We have classic race condition here. If relogin.jsp will 
be requested last, then issue is not reproducible, if some GIF will be 
requested and saved last issue will be reproducible.

Please let me know if any extra loggers required, will enable and shared with 
you.

Thanks and Regards,
Rajendra Rathore

RE: issue with Form based authentication

[Rathore, Rajendra]

Link for image where it will shows the details

https://docs.google.com/document/d/1Ziojwm6rPvyuJ6rpJR1tu0e5xTfnawrHeLz3QvL28XA/edit?usp=sharing


Thanks and Regards,
Rajendra Rathore
9922701491

From: Rathore, Rajendra
Sent: Thursday, December 30, 2021 4:25 PM
To: users@tomcat.apache.org
Subject: issue with Form based authentication
Importance: High

Hi Team,

We are facing some weird issue with tomcat Form based authentication, I will 
try to explain the scenario as below:

issue is reproducible in specific conditions, when browser cache is disabled, 
and cleared out before session timeout. In this conditions after session 
timeout when user is moving mouse over some elements where requests for GIFs 
are sent. Those request are processed by FormAuthenticator tomcat class. This 
class is responsible for saving requested URL and redirecting user to this 
saved URL after successful login. But this class saves in session all requests 
using the same key, this means that old requests are overrided by new ones. In 
this case there are multiple requests after session timeout, to get some GIFs, 
and to show relogin.jsp in popup window, those requests are handled by 
different threads, and last executed thread is saving to session information 
about requested URL. We have classic race condition here. If relogin.jsp will 
be requested last, then issue is not reproducible, if some GIF will be 
requested and saved last issue will be reproducible.

Please let me know if any extra loggers required, will enable and shared with 
you.

Thanks and Regards,
Rajendra Rathore

RE: Tomcat 9.0.81 Degraded ssl performance

[Rathore, Rajendra]

Hi Team,

Can you please share the release plan for 9.0.82 version, as we are planning to 
update it?

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: i...@flyingfischer.ch 
Sent: Thursday, October 12, 2023 10:54 AM
To: users@tomcat.apache.org
Subject: Re: Tomcat 9.0.81 Degraded ssl performance

Am 12.10.23 um 03:01 schrieb Paul Zepernick:
> Thank you Chuck
>
> Paul
> 
> From: Chuck Caldarale 
> Sent: Wednesday, October 11, 2023 8:54:59 PM
> To: Tomcat Users List 
> Subject: Re: Tomcat 9.0.81 Degraded ssl performance
>
> NOTICE: This email originated from outside of the organization. Do not click 
> links or open attachments unless you recognize the sender and know the 
> content is safe.
>
>> On Oct 11, 2023, at 19:44, Paul Zepernick  
>> wrote:
>>
>> Tomcat Version: 9.0.81
>> OS: Windows Server 2016
>>
>> We recently patched one of our QA servers to test 9.0.81 and ran into 
>> performance issues.  Page loads that normally take 1-2 seconds are now 
>> taking 50-60 seconds.  We were finally able to narrow the issue down to the 
>> SSL connector.  Adding an HTTP connector and bypassing ssl resolves the 
>> performance issue.  We have also tested rolling back to 9.0.80 with the same 
>> configuration and verified the issue does not exist.
>>
> This was due to a regression introduced in 9.0.81, as noted here:
> https://bz.a/
> pache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D67670=05%7C01%7Crarath
> ore%40ptc.com%7C1792927bf49742d936b208dbcae3a63e%7Cb9921086ff774d0d828
> acb3381f678e2%7C0%7C0%7C638326851325327468%7CUnknown%7CTWFpbGZsb3d8eyJ
> WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000
> %7C%7C%7C=jJCF0r%2F8vUBpRjc04kWHuGrRiOygwANqpVpfBKXQYEo%3D
> ved=0 2Fbz.apache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D67670=05%7C01%7C
> rarathore%40ptc.com%7C1792927bf49742d936b208dbcae3a63e%7Cb9921086ff774
> d0d828acb3381f678e2%7C0%7C0%7C638326851325483103%7CUnknown%7CTWFpbGZsb
> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
> 7C3000%7C%7C%7C=IHAB3t%2B41LTsxAYh6uwFx7sa7gy%2F7Our4b%2Fj56FELA
> s%3D=0>
>
> The problem has been fixed in 9.0.82 which is currently being voted on; 
> release will likely occur in another day or two.
>
>- Chuck
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or entity
> to which it is addressed. If the reader of this e-mail is not the
> intended recipient or intended recipient's authorized agent, the
> reader is hereby notified that any dissemination, distribution or
> copying of this e-mail is prohibited. If you have received this e-mail
> in error, please notify the sender by replying to this message and delete 
> this e-mail immediately.

You may also set on the connector as a workaround

compression="off"

This will resolve the issue for the time being without the need to downgrade to 
an insecure version.


Markus




-
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: Tomcat 9.0.81 Degraded ssl performance

[Rathore, Rajendra]

Hi Rémy,

Thanks for sharing the information but by when it is available on tomcat Home 
page https://tomcat.apache.org/? or is it safe to update this tomcat(9.0.82) to 
production version ?

Thanks and Regards,
Rajendra Rathore
9922701491

-Original Message-
From: Rémy Maucherat 
Sent: Friday, October 13, 2023 1:04 PM
To: Tomcat Users List 
Subject: Re: Tomcat 9.0.81 Degraded ssl performance

On Fri, Oct 13, 2023 at 9:25 AM Rathore, Rajendra  wrote:
>
> Hi Team,
>
> Can you please share the release plan for 9.0.82 version, as we are planning 
> to update it?

You can get it at the usual place: https://tomcat.apache.org/download-90.cgi

Rémy

>
> Thanks and Regards,
> Rajendra Rathore
> 9922701491
>
> -Original Message-
> From: i...@flyingfischer.ch 
> Sent: Thursday, October 12, 2023 10:54 AM
> To: users@tomcat.apache.org
> Subject: Re: Tomcat 9.0.81 Degraded ssl performance
>
> Am 12.10.23 um 03:01 schrieb Paul Zepernick:
> > Thank you Chuck
> >
> > Paul
> > 
> > From: Chuck Caldarale 
> > Sent: Wednesday, October 11, 2023 8:54:59 PM
> > To: Tomcat Users List 
> > Subject: Re: Tomcat 9.0.81 Degraded ssl performance
> >
> > NOTICE: This email originated from outside of the organization. Do not 
> > click links or open attachments unless you recognize the sender and know 
> > the content is safe.
> >
> >> On Oct 11, 2023, at 19:44, Paul Zepernick  
> >> wrote:
> >>
> >> Tomcat Version: 9.0.81
> >> OS: Windows Server 2016
> >>
> >> We recently patched one of our QA servers to test 9.0.81 and ran into 
> >> performance issues.  Page loads that normally take 1-2 seconds are now 
> >> taking 50-60 seconds.  We were finally able to narrow the issue down to 
> >> the SSL connector.  Adding an HTTP connector and bypassing ssl resolves 
> >> the performance issue.  We have also tested rolling back to 9.0.80 with 
> >> the same configuration and verified the issue does not exist.
> >>
> > This was due to a regression introduced in 9.0.81, as noted here:
> > https://bz/
> > .a%2F=05%7C01%7Crarathore%40ptc.com%7C3432f780a6f346997a3e08dbc
> > bbedd70%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C638327792861320
> > 216%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> > TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=024RK4UFHLTSrrfI7JO
> > qRlHbMHjvFQN7qvH5hEUIUW4%3D=0
> > pache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D67670=05%7C01%7Crara
> > th
> > ore%40ptc.com%7C1792927bf49742d936b208dbcae3a63e%7Cb9921086ff774d0d8
> > 28
> > acb3381f678e2%7C0%7C0%7C638326851325327468%7CUnknown%7CTWFpbGZsb3d8e
> > yJ
> > WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C30
> > 00
> > %7C%7C%7C=jJCF0r%2F8vUBpRjc04kWHuGrRiOygwANqpVpfBKXQYEo%3D
> > er
> > ved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%252
> > F%25
> > 2Fbz.apache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D67670=05%7C01%
> > 7C
> > rarathore%40ptc.com%7C1792927bf49742d936b208dbcae3a63e%7Cb9921086ff7
> > 74
> > d0d828acb3381f678e2%7C0%7C0%7C638326851325483103%7CUnknown%7CTWFpbGZ
> > sb
> > 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
> > D%
> > 7C3000%7C%7C%7C=IHAB3t%2B41LTsxAYh6uwFx7sa7gy%2F7Our4b%2Fj56FE
> > LA
> > s%3D=0>
> >
> > The problem has been fixed in 9.0.82 which is currently being voted on; 
> > release will likely occur in another day or two.
> >
> >- Chuck
> >
> > This e-mail, including attachments, may include confidential and/or
> > proprietary information, and may be used only by the person or
> > entity to which it is addressed. If the reader of this e-mail is not
> > the intended recipient or intended recipient's authorized agent, the
> > reader is hereby notified that any dissemination, distribution or
> > copying of this e-mail is prohibited. If you have received this
> > e-mail in error, please notify the sender by replying to this message and 
> > delete this e-mail immediately.
>
> You may also set on the connector as a workaround
>
> compression="off"
>
> This will resolve the issue for the time being without the need to downgrade 
> to an insecure version.
>
>
> Markus
>
>
>
>
> -
> 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

impact of setting autoDeploy="false" in server.xml

[Rathore, Rajendra]

Hi Team,

Please let me know the impact of setting autoDeploy="false" in server.xml 
files. Some of them I might aware like autodeploy is not going to work, impact 
for day light.

I ready some blogs and they saying that for production server you need to set 
the property to false, please confirm the same as you are the expert of this 
area.



Thanks and Regards,
Rajendra Rathore
9922701491

tomcat version retirement plan

[Rathore, Rajendra]

Hi Team,

Can you please share the timeline for retiring the individual tomcat release ?

Tomcat retirement plan date(tentative)
8.5.x
9.x.x
10.0.x
10.1.x

Based on above table we will plan which tomcat is long term supported so that 
we can use it for our software.

Thanks and Regards,
Rajendra Rathore
9922701491

need features list that were removed in tomcat 10 while moving from tomcat 9

[Rathore, Rajendra]

Hi,

We are migrating from tomcat 9 to tomcat 10, we run the migration tool on our 
codebase, that work perfectly, can you please share the changes from 9 to 10, 
we are interested in removed API or features that we can fix manually as 
migrator tool not take care of such changes.

Thanks and Regards,
Rajendra Rathore
9922701491