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://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 <rarath...@ptc.com>
Sent: 01 November 2018 06:10 PM
To: Tomcat Users List <users@tomcat.apache.org>
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 <guang.chao.1...@gmail.com>
Sent: 01 November 2018 06:07 PM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: precompile JSPs failure issue - Tomcat community
On Thu, Nov 1, 2018 at 7:13 PM Rathore, Rajendra <rarath...@ptc.com> 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 <guang.chao.1...@gmail.com>
Sent: 01 November 2018 03:41 PM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: precompile JSPs failure issue - Tomcat community
On Thu, Nov 1, 2018 at 5:33 PM Mark Thomas <ma...@apache.org> 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%3D53011&data=02%7C01%7Crar
athore%40ptc.com%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0d
828acb3381f678e2%7C0%7C0%7C636766727188877636&sdata=diEmx1WNaWPvH%
2FGMd8Ex%2B4AgZCaGxcC6fez5UD%2FEF1c%3D&reserved=0
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.ap
ache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D53492&data=02%7C01%7Crar
athore%40ptc.com%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0d
828acb3381f678e2%7C0%7C0%7C636766727188877636&sdata=rl1N7m5upe4E7A
3zTAx4oht2cjUHfuDoNCWoOHKfkrs%3D&reserved=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-date&data=02%7C01%7Crarathore%40ptc.co
m%7Cc0bce30fc877421ebd6808d63ff6f1f2%7Cb9921086ff774d0d828acb3381f678e
2%7C0%7C0%7C636766727188877636&sdata=lEQmu2kFIquRsA5rAeVw17HYosy6O
03GGZvt6d6CWCA%3D&reserved=0
--
Guang
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjavadevnotes.com%2Fjava-string-compare&data=02%7C01%7Crarathore%40ptc.com%7Ce055c122a344402f19ff08d63ff74502%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C636766728579713014&sdata=wcK%2FUGcxwfCAgJVNS4TvabtLLsGavYUKrEON1uDUpCQ%3D&reserved=0>
B KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB [
X ܚX KK[XZ[
\ \ ][ X ܚX P X ]
\X K ܙ B ܈Y][ۘ[ [X[ K[XZ[
\ \ Z[ X ]
\X K ܙ B
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. 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.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
