You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Prateek <pr...@gmail.com> on 2018/06/26 03:20:53 UTC
problem in starting tomcat
Hi,
My configuration:
OS:REDHAT 7.5 (64 bit)
Tomcat: 8.5.31
Jdk- jdk-11(Early-Access)
When I am trying to start my server I got following error as:
A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412
#
# JRE version: (11.0+18) (build )
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11-ea+18, mixed mode, aot, sharing, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C [libc.so.6+0x8128a] strlen+0x2a
#
# Core dump will be written. Default location: /localdisk/corefiles/core.%h.%e.%p
#
# An error report file with more information is saved as:
# /localdisk/corefiles/hs_err_pid2412.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
#
# -XX:OnError="/usr/bin/sudo /opt/CSCOcpm/bin/isegencore.sh %p"
# Executing /bin/sh -c "/usr/bin/sudo /opt/CSCOcpm/bin/isegencore.sh 2412" ...
Generating core file on Tue Jun 26 03:09:07 UTC 2018
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x00007fd4f23a441c in waitpid () from /lib64/libpthread.so.0
Missing separate debuginfos, use: debuginfo-install CSCOcpm-common-2.5.0-185.x86_64
warning: target file /proc/2412/cmdline contained unexpected null characters
Saved corefile core.2412
Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option PermSize; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
Reloading service
Waiting 60 s to prevent looping
Pls help I stuck at it.
Thanks & regards
Prateek
Sent from Mail for Windows 10
Sent from Mail for Windows 10
RE: problem in starting tomcat
Posted by Jäkel,
Guido <G....@dnb.de>.
>> When I am trying to start my server I got following error as:
>> A fatal error has been detected by the Java Runtime Environment:
>> #
>> # SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412
>> #
>> # JRE version: (11.0+18) (build )
>> # Java VM: Java HotSpot(TM) 64-Bit Server VM (11-ea+18, mixed mode, aot, sharing, tiered, compressed oops, g1 gc, linux-amd64)
>> # Problematic frame:
>> # C [libc.so.6+0x8128a] strlen+0x2a
>
>This is saying that the segfault occurred in libc code, specifically the
>strlen function. This suggests that either the JVM is using the libc
>library incorrectly, or that the libc library on your system is bad.
From your hs_er_pid.txt I read:
--------------- S Y S T E M ---------------
OS:Red Hat Enterprise Linux Server release 7.5 (Maipo)
uname:Linux 3.10.0-693.el7.x86_64 #1 SMP Thu Jul 6 19:56:57 EDT 2017 x86_64
libc:glibc 2.19 NPTL 2.19
[...]
vm_info: Java HotSpot(TM) 64-Bit Server VM (11-ea+18) for linux-amd64 JRE (11-ea+18), built on Jun 13 2018 20:25:53 by "mach5one" with gcc 7.3.0
So you're providing a somewhat older glibc 2.19 (released 20140208) but the JVM you're using was built recently (20180513). Did you compile this JVM? Was it compiled against a fittig version of glibc? I would strongly suggest to use a JRE/JDK package provided by your Linux Distribution.
Greetings
Guido
Re: problem in starting tomcat
Posted by Shawn Heisey <ap...@elyograg.org>.
On 6/25/2018 9:20 PM, Prateek wrote:
> My configuration:
> OS:REDHAT 7.5 (64 bit)
> Tomcat: 8.5.31
> Jdk- jdk-11(Early-Access)
+1 to everything else you've been told on this thread.
More stuff inline below.
> When I am trying to start my server I got following error as:
> A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412
> #
> # JRE version: (11.0+18) (build )
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (11-ea+18, mixed mode, aot, sharing, tiered, compressed oops, g1 gc, linux-amd64)
> # Problematic frame:
> # C [libc.so.6+0x8128a] strlen+0x2a
This is saying that the segfault occurred in libc code, specifically the
strlen function. This suggests that either the JVM is using the libc
library incorrectly, or that the libc library on your system is bad.
> # An error report file with more information is saved as:
> # /localdisk/corefiles/hs_err_pid2412.log
Can you provide the JVM error file above (or the one from the most
recent crash)?
> Saved corefile core.2412
If I had any idea how to interpret coredumps, I would ask for that file,
but I don't. Maybe Oracle can do something useful with it.
I did find a JDK bug showing a crash in libc, but that bug should be
fixed in Java 9 and later.
https://bugs.openjdk.java.net/browse/JDK-8186817
If the behavior is exactly the same with Java 10, then I would think it
means the system itself has a problem. My first thought would be that
the kernel or system libraries like libc are broken, but it could also
be faulty hardware. Can you get this working if you put Java 8 on THIS
system and use that?
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: problem in starting tomcat
Posted by Igal Sapir <is...@apache.org>.
On 6/27/2018 10:53 AM, Coty Sutherland wrote:
> On Wed, Jun 27, 2018 at 1:08 PM, Prateek <pr...@gmail.com> wrote:
>> Hi Chris,
>>
>> By hardened, I meant that support for some FIPS non-complaint algos were
>> removed/disabled.
>>
>> Thanks for confirming again that this is a clear problem with the JVM.
> From what you've given us this is a JVM problem and nothing that we can fix
> for you. At this point, we're just trying to verify that you get the same
> issue on a stable JVM as you do with the Java 11 Early Access release.
>
>> While the current version of Java is 10, as per the support roadmap at
>> http://www.oracle.com/technetwork/java/javase/eol-135779.html
>> the support for Java 10 ends within 6 months of end of support for Java
>> 8. We are trying to have our product ship with the version of Java, which
>> has support availability beyond these timelines.
>>
>> I have tried running with Java 10 and hit the same issue. I am not sure
>> about the Java 11.super-alpha that you were referring to. Can you please
>> point me in that direction.
> Please provide the hs_err_pid from a run with Java 10 so that we can verify
> that the failure is the same.
On 6/27/2018 9:18 AM, Prateek wrote:
> http://tomcat.apache.org/whichversion.html
>
> The above link suggests that tomcat generally works with any Java early access builds and hence the attempt to run using JDK11 EA build. Please suggest on the course of action that I should be taking.
I agree with Chris and Coty.
The statement that "Tomcat generally works with any Java version that
complies with the minimum requirements" is correct, but that is based on
the premise that the Java version does not have bugs that would prevent
Tomcat from running.
The problem with EA/Alpha/Beta builds is that they are not well tested
yet, and any "improvement" in the new version might introduce a new bug
that will cause such an issue.
It is also possible that a bug was introduced in Java 9 or 10 and your
specific set up triggers it while for most users there are no issues so
it hasn't been reported or fixed yet.
Igal
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: problem in starting tomcat
Posted by Coty Sutherland <cs...@apache.org>.
On Wed, Jun 27, 2018 at 1:08 PM, Prateek <pr...@gmail.com> wrote:
> Hi Chris,
>
> By hardened, I meant that support for some FIPS non-complaint algos were
> removed/disabled.
>
> Thanks for confirming again that this is a clear problem with the JVM.
>
From what you've given us this is a JVM problem and nothing that we can fix
for you. At this point, we're just trying to verify that you get the same
issue on a stable JVM as you do with the Java 11 Early Access release.
>
> While the current version of Java is 10, as per the support roadmap at
> http://www.oracle.com/technetwork/java/javase/eol-135779.html
> the support for Java 10 ends within 6 months of end of support for Java
> 8. We are trying to have our product ship with the version of Java, which
> has support availability beyond these timelines.
>
> I have tried running with Java 10 and hit the same issue. I am not sure
> about the Java 11.super-alpha that you were referring to. Can you please
> point me in that direction.
>
Please provide the hs_err_pid from a run with Java 10 so that we can verify
that the failure is the same.
>
> Thanks and Regards,
> Prateek.
>
> From: Christopher Schultz
> Sent: Wednesday, June 27, 2018 10:04 PM
> To: users@tomcat.apache.org
> Subject: Re: problem in starting tomcat
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Prateek,
>
> On 6/27/18 12:04 PM, Prateek wrote:
> > Hi Chris,
> >
> > We are running, libtcnative version 1.2.16 with apr version 1.6.3,
> > compiled from the source, configured to use a hardened version of
> > OpenSSL version 1.0.2.
>
> (LOL hardened OpenSSL)
>
> Given your full crash-dump, it's clear it's a problem with the JVM,
> though. Your use of libtcnative appears to be irrelevant.
>
> > Also, we have tried using the release quality JVM build
> > (1.8.0_162) and have no issues with launching tomcat with that.
> > (Assume that we can take this for hw being good)
>
> So when you use a JVM that's expected to work, it works? Great.
>
> > We are preparing for moving to the latest version of JRE available
> > given that support for Java 8 is going to end soon.
>
> Sure, support for Java 8 ends soon, but the current version of Java is
> 10, not 11.
>
> What happens when you run with Java 10.stable instead of Java
> 11.super-alpha?
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlszvJ4ACgkQHPApP6U8
> pFg9KRAAyJZMLi2mw1dItLi2QGwZmOw8uenFECwhrdYVnmSZNH3QvnWGm5+50fQC
> AsZJft984pezFBf7ASWd6GsjdoBRRDpb6x2WBODe2BvpdwBw9vcIDjGgR/9mNoxE
> /Bj62wydfLBuOxIOCIBLa2St7ktPglnyLXwWn6c1hwK3CzjBSaiUx9TTPBil8ym1
> w8JI2Y9kH0fuY69BfpLm1Sj6jnsXtsF0PUZF93tCd8cfUImMUwGaUjXWm35xNfFK
> k5FxIlG+oATbiBpntsd14EUyBqGDiLVKuv1kBf1medXakd09IRb9tKGVK0Dm64AP
> xGghDjPF7ugrQTX682hrOBYM+OjH5AFrHsOp505nnb+5AJEukmSDljeeYq2IWCiy
> YSCuN4j6jD5wi/PzEQ3h/hfX8RwAH4RARu1DYIMU+f6oA6RYmVT76Hn1tbkhT2Qb
> wKZsEfZ4EzaCIqwK0a6ZEkp1zCuxYoJWZwp0YTc/ROI2wB1iHqgJEVxBS/VF6UX9
> W+8GlPPVJu6ydlWau4J5f9X4t+BSiWs4EEiJlSfNZ8IsYwBMa4EK1jR1nbg2PAe5
> h5QLFg2zGa+1hxFLb1YredQKEtf1EIcvuZjrcVCpAHK1RgJBxBhKdzE4LaBAwMw8
> zqOZCnGlLWbfMxiRLWOG3wxuyorvU1aLwHDutbh3IJYAtryuTrY=
> =J+nk
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
RE: problem in starting tomcat
Posted by Prateek <pr...@gmail.com>.
Hi Chris,
By hardened, I meant that support for some FIPS non-complaint algos were removed/disabled.
Thanks for confirming again that this is a clear problem with the JVM.
While the current version of Java is 10, as per the support roadmap at http://www.oracle.com/technetwork/java/javase/eol-135779.html
the support for Java 10 ends within 6 months of end of support for Java 8. We are trying to have our product ship with the version of Java, which has support availability beyond these timelines.
I have tried running with Java 10 and hit the same issue. I am not sure about the Java 11.super-alpha that you were referring to. Can you please point me in that direction.
Thanks and Regards,
Prateek.
From: Christopher Schultz
Sent: Wednesday, June 27, 2018 10:04 PM
To: users@tomcat.apache.org
Subject: Re: problem in starting tomcat
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Prateek,
On 6/27/18 12:04 PM, Prateek wrote:
> Hi Chris,
>
> We are running, libtcnative version 1.2.16 with apr version 1.6.3,
> compiled from the source, configured to use a hardened version of
> OpenSSL version 1.0.2.
(LOL hardened OpenSSL)
Given your full crash-dump, it's clear it's a problem with the JVM,
though. Your use of libtcnative appears to be irrelevant.
> Also, we have tried using the release quality JVM build
> (1.8.0_162) and have no issues with launching tomcat with that.
> (Assume that we can take this for hw being good)
So when you use a JVM that's expected to work, it works? Great.
> We are preparing for moving to the latest version of JRE available
> given that support for Java 8 is going to end soon.
Sure, support for Java 8 ends soon, but the current version of Java is
10, not 11.
What happens when you run with Java 10.stable instead of Java
11.super-alpha?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlszvJ4ACgkQHPApP6U8
pFg9KRAAyJZMLi2mw1dItLi2QGwZmOw8uenFECwhrdYVnmSZNH3QvnWGm5+50fQC
AsZJft984pezFBf7ASWd6GsjdoBRRDpb6x2WBODe2BvpdwBw9vcIDjGgR/9mNoxE
/Bj62wydfLBuOxIOCIBLa2St7ktPglnyLXwWn6c1hwK3CzjBSaiUx9TTPBil8ym1
w8JI2Y9kH0fuY69BfpLm1Sj6jnsXtsF0PUZF93tCd8cfUImMUwGaUjXWm35xNfFK
k5FxIlG+oATbiBpntsd14EUyBqGDiLVKuv1kBf1medXakd09IRb9tKGVK0Dm64AP
xGghDjPF7ugrQTX682hrOBYM+OjH5AFrHsOp505nnb+5AJEukmSDljeeYq2IWCiy
YSCuN4j6jD5wi/PzEQ3h/hfX8RwAH4RARu1DYIMU+f6oA6RYmVT76Hn1tbkhT2Qb
wKZsEfZ4EzaCIqwK0a6ZEkp1zCuxYoJWZwp0YTc/ROI2wB1iHqgJEVxBS/VF6UX9
W+8GlPPVJu6ydlWau4J5f9X4t+BSiWs4EEiJlSfNZ8IsYwBMa4EK1jR1nbg2PAe5
h5QLFg2zGa+1hxFLb1YredQKEtf1EIcvuZjrcVCpAHK1RgJBxBhKdzE4LaBAwMw8
zqOZCnGlLWbfMxiRLWOG3wxuyorvU1aLwHDutbh3IJYAtryuTrY=
=J+nk
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: problem in starting tomcat
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Prateek,
On 6/27/18 12:04 PM, Prateek wrote:
> Hi Chris,
>
> We are running, libtcnative version 1.2.16 with apr version 1.6.3,
> compiled from the source, configured to use a hardened version of
> OpenSSL version 1.0.2.
(LOL hardened OpenSSL)
Given your full crash-dump, it's clear it's a problem with the JVM,
though. Your use of libtcnative appears to be irrelevant.
> Also, we have tried using the release quality JVM build
> (1.8.0_162) and have no issues with launching tomcat with that.
> (Assume that we can take this for hw being good)
So when you use a JVM that's expected to work, it works? Great.
> We are preparing for moving to the latest version of JRE available
> given that support for Java 8 is going to end soon.
Sure, support for Java 8 ends soon, but the current version of Java is
10, not 11.
What happens when you run with Java 10.stable instead of Java
11.super-alpha?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlszvJ4ACgkQHPApP6U8
pFg9KRAAyJZMLi2mw1dItLi2QGwZmOw8uenFECwhrdYVnmSZNH3QvnWGm5+50fQC
AsZJft984pezFBf7ASWd6GsjdoBRRDpb6x2WBODe2BvpdwBw9vcIDjGgR/9mNoxE
/Bj62wydfLBuOxIOCIBLa2St7ktPglnyLXwWn6c1hwK3CzjBSaiUx9TTPBil8ym1
w8JI2Y9kH0fuY69BfpLm1Sj6jnsXtsF0PUZF93tCd8cfUImMUwGaUjXWm35xNfFK
k5FxIlG+oATbiBpntsd14EUyBqGDiLVKuv1kBf1medXakd09IRb9tKGVK0Dm64AP
xGghDjPF7ugrQTX682hrOBYM+OjH5AFrHsOp505nnb+5AJEukmSDljeeYq2IWCiy
YSCuN4j6jD5wi/PzEQ3h/hfX8RwAH4RARu1DYIMU+f6oA6RYmVT76Hn1tbkhT2Qb
wKZsEfZ4EzaCIqwK0a6ZEkp1zCuxYoJWZwp0YTc/ROI2wB1iHqgJEVxBS/VF6UX9
W+8GlPPVJu6ydlWau4J5f9X4t+BSiWs4EEiJlSfNZ8IsYwBMa4EK1jR1nbg2PAe5
h5QLFg2zGa+1hxFLb1YredQKEtf1EIcvuZjrcVCpAHK1RgJBxBhKdzE4LaBAwMw8
zqOZCnGlLWbfMxiRLWOG3wxuyorvU1aLwHDutbh3IJYAtryuTrY=
=J+nk
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: problem in starting tomcat
Posted by Prateek <pr...@gmail.com>.
Hi Chris,
We are running, libtcnative version 1.2.16 with apr version 1.6.3, compiled from the source, configured to use a hardened version of OpenSSL version 1.0.2.
Also, we have tried using the release quality JVM build (1.8.0_162) and have no issues with launching tomcat with that. (Assume that we can take this for hw being good)
We are preparing for moving to the latest version of JRE available given that support for Java 8 is going to end soon.
Please suggest.
Regards,
Prateek
From: Christopher Schultz
Sent: Tuesday, June 26, 2018 9:40 PM
To: users@tomcat.apache.org
Subject: Re: problem in starting tomcat
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Prateek,
On 6/25/18 11:20 PM, Prateek wrote:
> Hi, My configuration: OS:REDHAT 7.5 (64 bit) Tomcat: 8.5.31 Jdk-
> jdk-11(Early-Access)
>
> When I am trying to start my server I got following error as: A
> fatal error has been detected by the Java Runtime Environment: # #
> SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412 # # JRE
> version: (11.0+18) (build ) # Java VM: Java HotSpot(TM) 64-Bit
> Server VM (11-ea+18, mixed mode, aot, sharing, tiered, compressed
> oops, g1 gc, linux-amd64) # Problematic frame: # C
> [libc.so.6+0x8128a] strlen+0x2a
Are you running any custom native code (including libtcnative)? If
not, either the JVM or your hardware is to blame.
First, I'd re-try with a release-quality JVM build instead of the
"early access" build, which may have some bugs in it. If that doesn't
help, it's time to look at your hardware.
Run several rounds of memtest86+ on your hardware to see whether it
finds any errors. If you find errors, you have a hardware failure in
your CPU, motherboard, or memory, and you'll need to replace one or
more components.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlsyZV8ACgkQHPApP6U8
pFjRFw//XnOm0FrbRjc0ELxDiF/uuWCAEHHKjMjEBat04DG6TTMwTAUikmm0wTXR
2oecK+zU/Zc2cgN6i/pFagUbjeNz1WxHfKmsBK6w2loyLlkJ0WZfmaVhAB7NCbep
njp+OtdtDXoQb+wegkQddihDXGhnUEMszMKdPOTvOJEk5dbY7vNIX7a7ktOVseMu
hsbggpUtrz8DHwe8BwiOmCK7L5VCdfjMWG23rSPustulVQEu34bKKB9p6ke/cQwg
KWuWOa0yPQk1RRu9Fue9mqI+ppQVpVb6bZ6nqmlktCtqQ7sS5A4Pyx794/Kht5bs
xKZd+CmxS1+hDTBCTpfIhHbo+r7RXiJ2yOP+/VIzOPTMb+wLUGIgjbSM2opeUC62
S0YaqWVzUseMbivZVMxC+S4kTiabM1Dr7MbXtEf6Gu3QrybB7epwImO+l98t+Jjg
nY0WIXS+8FdZHoNpItliUjj6ciPNtVUFubghYQAKsn5tHUx+s6Tcos2kEnUPsm6N
RMpKb2fBEs9DJTa2GCAHRsSPVE9daDJsDxm5yP8h5AQd82QpSj2s2KoX7oTZ8rV3
3pYfi4nNIXm+6y/HmQG3oU1MYui4i4wHrgSeuFOD80/JkKQhwDwvEz7gFe3ui06U
KN3jnT6YIlFGvurfw1r9ZRBLeDVrdyzqu92ot4NtfCkRKdoBUNg=
=2XQn
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: problem in starting tomcat
Posted by Prateek <pr...@gmail.com>.
Hi Igal,
I have removed the permSize and maxPermSize settings and tried launch tomcat. This resulted in the crash, though I no longer see the warning message in catalina.out about those options.
http://tomcat.apache.org/whichversion.html
The above link suggests that tomcat generally works with any Java early access builds and hence the attempt to run using JDK11 EA build. Please suggest on the course of action that I should be taking.
Regards,
Prateek.
From: Igal Sapir
Sent: Tuesday, June 26, 2018 10:21 PM
To: users@tomcat.apache.org
Subject: Re: problem in starting tomcat
Prateek,
On 6/26/2018 9:27 AM, Prateek Yadav wrote:
> Thanks for reply
> I already tested it for more than one machine so hardware problem can not
> be a case.
On 6/25/2018 8:20 PM, Prateek wrote:
> My configuration:
> OS:REDHAT 7.5 (64 bit)
> Tomcat: 8.5.31
> Jdk- jdk-11(Early-Access)
>
> When I am trying to start my server I got following error as:
> A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412
> #
> # JRE version: (11.0+18) (build )
> # <snip/>
> Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option PermSize; support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
You are running Java 11EA but your config settings seem to be circa Java
7 (per PermSize warnings).
I second Chris' suggestion to use a well tested "release version" of the
JVM, but at the very least you should try to remove all of the
unnecessary config settings.
Igal
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: problem in starting tomcat
Posted by Igal Sapir <is...@apache.org>.
Prateek,
On 6/26/2018 9:27 AM, Prateek Yadav wrote:
> Thanks for reply
> I already tested it for more than one machine so hardware problem can not
> be a case.
On 6/25/2018 8:20 PM, Prateek wrote:
> My configuration:
> OS:REDHAT 7.5 (64 bit)
> Tomcat: 8.5.31
> Jdk- jdk-11(Early-Access)
>
> When I am trying to start my server I got following error as:
> A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412
> #
> # JRE version: (11.0+18) (build )
> # <snip/>
> Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option PermSize; support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
You are running Java 11EA but your config settings seem to be circa Java
7 (per PermSize warnings).
I second Chris' suggestion to use a well tested "release version" of the
JVM, but at the very least you should try to remove all of the
unnecessary config settings.
Igal
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: problem in starting tomcat
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Prateek,
On 6/27/18 1:41 AM, Prateek wrote:
> Here I am hs_err_pid file
> Native frames: (J=compiled Java code, A=aot compiled Java code,
> j=interpreted, Vv=VM code, C=native code) C [libc.so.6+0x8128a]
> strlen+0x2a V [libjvm.so+0x6030f1]
> ClassLoader::setup_bootstrap_search_path()+0x111 V
> [libjvm.so+0x60377a] classLoader_init1()+0x4a V
> [libjvm.so+0x882549] init_globals()+0x39 V [libjvm.so+0xde4247]
> Threads::create_vm(JavaVMInitArgs*, bool*)+0x327 V
> [libjvm.so+0x93f652] JNI_CreateJavaVM+0x52
>
This is 100% a JVM bug. It's crashing while trying to start itself up.
Try a release-quality JVM version.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlszj1AACgkQHPApP6U8
pFhtWw/+ONTDCmECD56tseXbi5ru+VBxZn9mlkVUlHzjHx7vVBVhdnYpkUu4hDqT
W4XB5/g5gSp0oDOPEM+Z5kfSfSkXAO440s/JBgIoalMlP3SaYYgG0ECIxk1BKH9m
esTeGMj51rw4wADVW7OMkAaxbIz2tHv2GzLYn+H1QNYu76UjIGpnI7m4NKNDNo1X
I74z7LbSpKSLPiw/5pXKNzcVkS4MvV8SqMBp5hVBJdwTBMpUKgquXh9LV6gAtSW5
QQGwzp5jt9cY63duDk02XAohO1IPOILXRStnaZ7yzRS8C1a0/V4zn50jmLrzZoPJ
AvbLqrGQpb3kMPsbLRQBTuKaaEL3JR+MGfgTjPVz76kBuxFNlWSwP48Iy2Xl8tdL
h6Pmr5VLD35wkQQkHPogOJumOqBTsrsJk5BQb8XXXxWkQuRaH0DbP18z3jOdKXkz
nDLv9BqFuO9QmBX8f3R2isQGe4TToJ0MoUY+lldcONNfCkp2qVa9fCaWziLmaBzR
Zfq80sm17bOKzX6gjkM7Z/+RroE7ZGFVXimYz0gzLvGbdiDDulq3f/CSsaT0jqg/
JJIsr9K4tv88ACdppQwaqNWSFSiZK1HCcyiIinh8wgA9FqU4wrDOqKziGRKuSkA0
faO3xbptX01hnS2XZEMfHOM+pt0Nr7jyGDM0VrdtbQHMBrb/+l0=
=4O5C
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: problem in starting tomcat
Posted by Prateek <pr...@gmail.com>.
Here I am hs_err_pid file
Sent from Mail for Windows 10
From: Coty Sutherland
Sent: Tuesday, June 26, 2018 10:22 PM
To: Tomcat Users List
Subject: Re: problem in starting tomcat
On Tue, Jun 26, 2018 at 12:27 PM, Prateek Yadav <pr...@gmail.com>
wrote:
> Thanks for reply
> I already tested it for more than one machine so hardware problem can not
> be a case.
>
What happens if you don't specify that OnError call? Can you attach a
fuller stack trace if not the entire hs_err_pid log (make sure there isn't
anything sensitive in there)? If the JVM is crashing you should still get
an hs_err_pid log, but given that the crash is in libc and we don't know
what isegencore.sh is, removing it and getting a clearer stack trace would
be nice.
>
> On Tue, Jun 26, 2018, 9:40 PM Christopher Schultz <
> chris@christopherschultz.net> wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > Prateek,
> >
> > On 6/25/18 11:20 PM, Prateek wrote:
> > > Hi, My configuration: OS:REDHAT 7.5 (64 bit) Tomcat: 8.5.31 Jdk-
> > > jdk-11(Early-Access)
> > >
> > > When I am trying to start my server I got following error as: A
> > > fatal error has been detected by the Java Runtime Environment: # #
> > > SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412 # # JRE
> > > version: (11.0+18) (build ) # Java VM: Java HotSpot(TM) 64-Bit
> > > Server VM (11-ea+18, mixed mode, aot, sharing, tiered, compressed
> > > oops, g1 gc, linux-amd64) # Problematic frame: # C
> > > [libc.so.6+0x8128a] strlen+0x2a
> >
> > Are you running any custom native code (including libtcnative)? If
> > not, either the JVM or your hardware is to blame.
> >
> > First, I'd re-try with a release-quality JVM build instead of the
> > "early access" build, which may have some bugs in it. If that doesn't
> > help, it's time to look at your hardware.
> >
> > Run several rounds of memtest86+ on your hardware to see whether it
> > finds any errors. If you find errors, you have a hardware failure in
> > your CPU, motherboard, or memory, and you'll need to replace one or
> > more components.
> >
> > - -chris
> > -----BEGIN PGP SIGNATURE-----
> > Comment: GPGTools - http://gpgtools.org
> > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> >
> > iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlsyZV8ACgkQHPApP6U8
> > pFjRFw//XnOm0FrbRjc0ELxDiF/uuWCAEHHKjMjEBat04DG6TTMwTAUikmm0wTXR
> > 2oecK+zU/Zc2cgN6i/pFagUbjeNz1WxHfKmsBK6w2loyLlkJ0WZfmaVhAB7NCbep
> > njp+OtdtDXoQb+wegkQddihDXGhnUEMszMKdPOTvOJEk5dbY7vNIX7a7ktOVseMu
> > hsbggpUtrz8DHwe8BwiOmCK7L5VCdfjMWG23rSPustulVQEu34bKKB9p6ke/cQwg
> > KWuWOa0yPQk1RRu9Fue9mqI+ppQVpVb6bZ6nqmlktCtqQ7sS5A4Pyx794/Kht5bs
> > xKZd+CmxS1+hDTBCTpfIhHbo+r7RXiJ2yOP+/VIzOPTMb+wLUGIgjbSM2opeUC62
> > S0YaqWVzUseMbivZVMxC+S4kTiabM1Dr7MbXtEf6Gu3QrybB7epwImO+l98t+Jjg
> > nY0WIXS+8FdZHoNpItliUjj6ciPNtVUFubghYQAKsn5tHUx+s6Tcos2kEnUPsm6N
> > RMpKb2fBEs9DJTa2GCAHRsSPVE9daDJsDxm5yP8h5AQd82QpSj2s2KoX7oTZ8rV3
> > 3pYfi4nNIXm+6y/HmQG3oU1MYui4i4wHrgSeuFOD80/JkKQhwDwvEz7gFe3ui06U
> > KN3jnT6YIlFGvurfw1r9ZRBLeDVrdyzqu92ot4NtfCkRKdoBUNg=
> > =2XQn
> > -----END PGP SIGNATURE-----
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
>
RE: problem in starting tomcat
Posted by Prateek <pr...@gmail.com>.
Hi Coty,
I have tried after removing OnError from the JAVA_OPTS. The results are the same.
Please suggest.
Regards,
Prateek.
From: Coty Sutherland
Sent: Tuesday, June 26, 2018 10:22 PM
To: Tomcat Users List
Subject: Re: problem in starting tomcat
On Tue, Jun 26, 2018 at 12:27 PM, Prateek Yadav <pr...@gmail.com>
wrote:
> Thanks for reply
> I already tested it for more than one machine so hardware problem can not
> be a case.
>
What happens if you don't specify that OnError call? Can you attach a
fuller stack trace if not the entire hs_err_pid log (make sure there isn't
anything sensitive in there)? If the JVM is crashing you should still get
an hs_err_pid log, but given that the crash is in libc and we don't know
what isegencore.sh is, removing it and getting a clearer stack trace would
be nice.
>
> On Tue, Jun 26, 2018, 9:40 PM Christopher Schultz <
> chris@christopherschultz.net> wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > Prateek,
> >
> > On 6/25/18 11:20 PM, Prateek wrote:
> > > Hi, My configuration: OS:REDHAT 7.5 (64 bit) Tomcat: 8.5.31 Jdk-
> > > jdk-11(Early-Access)
> > >
> > > When I am trying to start my server I got following error as: A
> > > fatal error has been detected by the Java Runtime Environment: # #
> > > SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412 # # JRE
> > > version: (11.0+18) (build ) # Java VM: Java HotSpot(TM) 64-Bit
> > > Server VM (11-ea+18, mixed mode, aot, sharing, tiered, compressed
> > > oops, g1 gc, linux-amd64) # Problematic frame: # C
> > > [libc.so.6+0x8128a] strlen+0x2a
> >
> > Are you running any custom native code (including libtcnative)? If
> > not, either the JVM or your hardware is to blame.
> >
> > First, I'd re-try with a release-quality JVM build instead of the
> > "early access" build, which may have some bugs in it. If that doesn't
> > help, it's time to look at your hardware.
> >
> > Run several rounds of memtest86+ on your hardware to see whether it
> > finds any errors. If you find errors, you have a hardware failure in
> > your CPU, motherboard, or memory, and you'll need to replace one or
> > more components.
> >
> > - -chris
> > -----BEGIN PGP SIGNATURE-----
> > Comment: GPGTools - http://gpgtools.org
> > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> >
> > iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlsyZV8ACgkQHPApP6U8
> > pFjRFw//XnOm0FrbRjc0ELxDiF/uuWCAEHHKjMjEBat04DG6TTMwTAUikmm0wTXR
> > 2oecK+zU/Zc2cgN6i/pFagUbjeNz1WxHfKmsBK6w2loyLlkJ0WZfmaVhAB7NCbep
> > njp+OtdtDXoQb+wegkQddihDXGhnUEMszMKdPOTvOJEk5dbY7vNIX7a7ktOVseMu
> > hsbggpUtrz8DHwe8BwiOmCK7L5VCdfjMWG23rSPustulVQEu34bKKB9p6ke/cQwg
> > KWuWOa0yPQk1RRu9Fue9mqI+ppQVpVb6bZ6nqmlktCtqQ7sS5A4Pyx794/Kht5bs
> > xKZd+CmxS1+hDTBCTpfIhHbo+r7RXiJ2yOP+/VIzOPTMb+wLUGIgjbSM2opeUC62
> > S0YaqWVzUseMbivZVMxC+S4kTiabM1Dr7MbXtEf6Gu3QrybB7epwImO+l98t+Jjg
> > nY0WIXS+8FdZHoNpItliUjj6ciPNtVUFubghYQAKsn5tHUx+s6Tcos2kEnUPsm6N
> > RMpKb2fBEs9DJTa2GCAHRsSPVE9daDJsDxm5yP8h5AQd82QpSj2s2KoX7oTZ8rV3
> > 3pYfi4nNIXm+6y/HmQG3oU1MYui4i4wHrgSeuFOD80/JkKQhwDwvEz7gFe3ui06U
> > KN3jnT6YIlFGvurfw1r9ZRBLeDVrdyzqu92ot4NtfCkRKdoBUNg=
> > =2XQn
> > -----END PGP SIGNATURE-----
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
>
Re: problem in starting tomcat
Posted by Coty Sutherland <cs...@apache.org>.
On Tue, Jun 26, 2018 at 12:27 PM, Prateek Yadav <pr...@gmail.com>
wrote:
> Thanks for reply
> I already tested it for more than one machine so hardware problem can not
> be a case.
>
What happens if you don't specify that OnError call? Can you attach a
fuller stack trace if not the entire hs_err_pid log (make sure there isn't
anything sensitive in there)? If the JVM is crashing you should still get
an hs_err_pid log, but given that the crash is in libc and we don't know
what isegencore.sh is, removing it and getting a clearer stack trace would
be nice.
>
> On Tue, Jun 26, 2018, 9:40 PM Christopher Schultz <
> chris@christopherschultz.net> wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > Prateek,
> >
> > On 6/25/18 11:20 PM, Prateek wrote:
> > > Hi, My configuration: OS:REDHAT 7.5 (64 bit) Tomcat: 8.5.31 Jdk-
> > > jdk-11(Early-Access)
> > >
> > > When I am trying to start my server I got following error as: A
> > > fatal error has been detected by the Java Runtime Environment: # #
> > > SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412 # # JRE
> > > version: (11.0+18) (build ) # Java VM: Java HotSpot(TM) 64-Bit
> > > Server VM (11-ea+18, mixed mode, aot, sharing, tiered, compressed
> > > oops, g1 gc, linux-amd64) # Problematic frame: # C
> > > [libc.so.6+0x8128a] strlen+0x2a
> >
> > Are you running any custom native code (including libtcnative)? If
> > not, either the JVM or your hardware is to blame.
> >
> > First, I'd re-try with a release-quality JVM build instead of the
> > "early access" build, which may have some bugs in it. If that doesn't
> > help, it's time to look at your hardware.
> >
> > Run several rounds of memtest86+ on your hardware to see whether it
> > finds any errors. If you find errors, you have a hardware failure in
> > your CPU, motherboard, or memory, and you'll need to replace one or
> > more components.
> >
> > - -chris
> > -----BEGIN PGP SIGNATURE-----
> > Comment: GPGTools - http://gpgtools.org
> > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> >
> > iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlsyZV8ACgkQHPApP6U8
> > pFjRFw//XnOm0FrbRjc0ELxDiF/uuWCAEHHKjMjEBat04DG6TTMwTAUikmm0wTXR
> > 2oecK+zU/Zc2cgN6i/pFagUbjeNz1WxHfKmsBK6w2loyLlkJ0WZfmaVhAB7NCbep
> > njp+OtdtDXoQb+wegkQddihDXGhnUEMszMKdPOTvOJEk5dbY7vNIX7a7ktOVseMu
> > hsbggpUtrz8DHwe8BwiOmCK7L5VCdfjMWG23rSPustulVQEu34bKKB9p6ke/cQwg
> > KWuWOa0yPQk1RRu9Fue9mqI+ppQVpVb6bZ6nqmlktCtqQ7sS5A4Pyx794/Kht5bs
> > xKZd+CmxS1+hDTBCTpfIhHbo+r7RXiJ2yOP+/VIzOPTMb+wLUGIgjbSM2opeUC62
> > S0YaqWVzUseMbivZVMxC+S4kTiabM1Dr7MbXtEf6Gu3QrybB7epwImO+l98t+Jjg
> > nY0WIXS+8FdZHoNpItliUjj6ciPNtVUFubghYQAKsn5tHUx+s6Tcos2kEnUPsm6N
> > RMpKb2fBEs9DJTa2GCAHRsSPVE9daDJsDxm5yP8h5AQd82QpSj2s2KoX7oTZ8rV3
> > 3pYfi4nNIXm+6y/HmQG3oU1MYui4i4wHrgSeuFOD80/JkKQhwDwvEz7gFe3ui06U
> > KN3jnT6YIlFGvurfw1r9ZRBLeDVrdyzqu92ot4NtfCkRKdoBUNg=
> > =2XQn
> > -----END PGP SIGNATURE-----
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
>
Re: problem in starting tomcat
Posted by Prateek Yadav <pr...@gmail.com>.
Thanks for reply
I already tested it for more than one machine so hardware problem can not
be a case.
On Tue, Jun 26, 2018, 9:40 PM Christopher Schultz <
chris@christopherschultz.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Prateek,
>
> On 6/25/18 11:20 PM, Prateek wrote:
> > Hi, My configuration: OS:REDHAT 7.5 (64 bit) Tomcat: 8.5.31 Jdk-
> > jdk-11(Early-Access)
> >
> > When I am trying to start my server I got following error as: A
> > fatal error has been detected by the Java Runtime Environment: # #
> > SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412 # # JRE
> > version: (11.0+18) (build ) # Java VM: Java HotSpot(TM) 64-Bit
> > Server VM (11-ea+18, mixed mode, aot, sharing, tiered, compressed
> > oops, g1 gc, linux-amd64) # Problematic frame: # C
> > [libc.so.6+0x8128a] strlen+0x2a
>
> Are you running any custom native code (including libtcnative)? If
> not, either the JVM or your hardware is to blame.
>
> First, I'd re-try with a release-quality JVM build instead of the
> "early access" build, which may have some bugs in it. If that doesn't
> help, it's time to look at your hardware.
>
> Run several rounds of memtest86+ on your hardware to see whether it
> finds any errors. If you find errors, you have a hardware failure in
> your CPU, motherboard, or memory, and you'll need to replace one or
> more components.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlsyZV8ACgkQHPApP6U8
> pFjRFw//XnOm0FrbRjc0ELxDiF/uuWCAEHHKjMjEBat04DG6TTMwTAUikmm0wTXR
> 2oecK+zU/Zc2cgN6i/pFagUbjeNz1WxHfKmsBK6w2loyLlkJ0WZfmaVhAB7NCbep
> njp+OtdtDXoQb+wegkQddihDXGhnUEMszMKdPOTvOJEk5dbY7vNIX7a7ktOVseMu
> hsbggpUtrz8DHwe8BwiOmCK7L5VCdfjMWG23rSPustulVQEu34bKKB9p6ke/cQwg
> KWuWOa0yPQk1RRu9Fue9mqI+ppQVpVb6bZ6nqmlktCtqQ7sS5A4Pyx794/Kht5bs
> xKZd+CmxS1+hDTBCTpfIhHbo+r7RXiJ2yOP+/VIzOPTMb+wLUGIgjbSM2opeUC62
> S0YaqWVzUseMbivZVMxC+S4kTiabM1Dr7MbXtEf6Gu3QrybB7epwImO+l98t+Jjg
> nY0WIXS+8FdZHoNpItliUjj6ciPNtVUFubghYQAKsn5tHUx+s6Tcos2kEnUPsm6N
> RMpKb2fBEs9DJTa2GCAHRsSPVE9daDJsDxm5yP8h5AQd82QpSj2s2KoX7oTZ8rV3
> 3pYfi4nNIXm+6y/HmQG3oU1MYui4i4wHrgSeuFOD80/JkKQhwDwvEz7gFe3ui06U
> KN3jnT6YIlFGvurfw1r9ZRBLeDVrdyzqu92ot4NtfCkRKdoBUNg=
> =2XQn
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: problem in starting tomcat
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Prateek,
On 6/25/18 11:20 PM, Prateek wrote:
> Hi, My configuration: OS:REDHAT 7.5 (64 bit) Tomcat: 8.5.31 Jdk-
> jdk-11(Early-Access)
>
> When I am trying to start my server I got following error as: A
> fatal error has been detected by the Java Runtime Environment: # #
> SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412 # # JRE
> version: (11.0+18) (build ) # Java VM: Java HotSpot(TM) 64-Bit
> Server VM (11-ea+18, mixed mode, aot, sharing, tiered, compressed
> oops, g1 gc, linux-amd64) # Problematic frame: # C
> [libc.so.6+0x8128a] strlen+0x2a
Are you running any custom native code (including libtcnative)? If
not, either the JVM or your hardware is to blame.
First, I'd re-try with a release-quality JVM build instead of the
"early access" build, which may have some bugs in it. If that doesn't
help, it's time to look at your hardware.
Run several rounds of memtest86+ on your hardware to see whether it
finds any errors. If you find errors, you have a hardware failure in
your CPU, motherboard, or memory, and you'll need to replace one or
more components.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlsyZV8ACgkQHPApP6U8
pFjRFw//XnOm0FrbRjc0ELxDiF/uuWCAEHHKjMjEBat04DG6TTMwTAUikmm0wTXR
2oecK+zU/Zc2cgN6i/pFagUbjeNz1WxHfKmsBK6w2loyLlkJ0WZfmaVhAB7NCbep
njp+OtdtDXoQb+wegkQddihDXGhnUEMszMKdPOTvOJEk5dbY7vNIX7a7ktOVseMu
hsbggpUtrz8DHwe8BwiOmCK7L5VCdfjMWG23rSPustulVQEu34bKKB9p6ke/cQwg
KWuWOa0yPQk1RRu9Fue9mqI+ppQVpVb6bZ6nqmlktCtqQ7sS5A4Pyx794/Kht5bs
xKZd+CmxS1+hDTBCTpfIhHbo+r7RXiJ2yOP+/VIzOPTMb+wLUGIgjbSM2opeUC62
S0YaqWVzUseMbivZVMxC+S4kTiabM1Dr7MbXtEf6Gu3QrybB7epwImO+l98t+Jjg
nY0WIXS+8FdZHoNpItliUjj6ciPNtVUFubghYQAKsn5tHUx+s6Tcos2kEnUPsm6N
RMpKb2fBEs9DJTa2GCAHRsSPVE9daDJsDxm5yP8h5AQd82QpSj2s2KoX7oTZ8rV3
3pYfi4nNIXm+6y/HmQG3oU1MYui4i4wHrgSeuFOD80/JkKQhwDwvEz7gFe3ui06U
KN3jnT6YIlFGvurfw1r9ZRBLeDVrdyzqu92ot4NtfCkRKdoBUNg=
=2XQn
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org