RE: Http2 tomact server taking time in responding when 1st StreamId is a large integer value like 2147483641
Thanks Mark.
Do we need to raise a bug for this?
Regards,
Prateek Kohli
-Original Message-
From: Mark Thomas
Sent: Thursday, May 21, 2020 8:43 PM
To: users@tomcat.apache.org
Subject: Re: Http2 tomact server taking time in responding when 1st StreamId is
a large integer value like 2147483641
On 21/05/2020 13:30, Prateek Kohli wrote:
> Hi,
>
> I debugged this further and the problem seems to be because of the below code
> in Http2UpgradeHandler class:
>
> private void closeIdleStreams(int newMaxActiveRemoteStreamId) throws
> Http2Exception {
> for (int i = maxActiveRemoteStreamId + 2; i <
> newMaxActiveRemoteStreamId; i += 2) {
> Stream stream = getStream(i, false);
> if (stream != null) {
> stream.closeIfIdle();
> }
> }
> maxActiveRemoteStreamId = newMaxActiveRemoteStreamId;
> }
>
> When we take 1st StreamId as 2147483641, the above loop takes around 4~5
> seconds to execute and hence, the response is delayed.
That is where I suspected the issue would be but hadn't got around to
confirming it. This will get fixed for the next release round (due in a couple
of weeks).
Mark
>
> Regards,
> Prateek Kohli
>
> -Original Message-
> From: Manuel Dominguez Sarmiento
> Sent: Thursday, May 21, 2020 3:34 PM
> To: Tomcat Users List ; Prateek Kohli
>
> Subject: Re: Http2 tomact server taking time in responding when 1st
> StreamId is a large integer value like 2147483641
>
> I must say that we're also seeing weird, seemingly random response
> delays from Tomcat on HTTP/2 We haven't looked into it at such a low
> level though. We're currently on
> 9.0.35 but we've been seeing this on previous versions as well.
>
> *Manuel Dominguez Sarmiento*
>
> On 21/05/2020 05:32, Prateek Kohli wrote:
>>
>> Hello,
>>
>> Tomcat version : 9.0.29
>>
>> We are running a Tomcat Http2 Server and a Jetty http2 client.
>>
>> When we send 1^st request from Jetty client to tomcat server with
>> streamId number as 1, tomcat sends the WINDOW_UPDATE header and the
>> response in 1~2 milliseconds.
>>
>> Packet number 164 is the response in the below tcpdump.
>>
>> But when we send the 1st request from jetty client to tomcat server
>> with streamId as 2147483641, the 1^st response from tomcat comes
>> after almost 5 seconds
>>
>> And the response for subsequent requests comes within 1~2 milliseconds.
>>
>> In the below tcpdump it can be seen that the response packet number
>> 167 comes after almost 5 seconds from the tomcat server.
>>
>> Would you please be able to explain why the response from tomcat
>> server is getting delayed when the 1^st StreamId number is a large
>> integer i.e. 2147483641.
>>
>> Regards,
>>
>> Prateek Kohli
>>
>
>
> -
> 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: Http2 tomact server taking time in responding when 1st StreamId is a large integer value like 2147483641
Hi,
I debugged this further and the problem seems to be because of the below code
in Http2UpgradeHandler class:
private void closeIdleStreams(int newMaxActiveRemoteStreamId) throws
Http2Exception {
for (int i = maxActiveRemoteStreamId + 2; i <
newMaxActiveRemoteStreamId; i += 2) {
Stream stream = getStream(i, false);
if (stream != null) {
stream.closeIfIdle();
}
}
maxActiveRemoteStreamId = newMaxActiveRemoteStreamId;
}
When we take 1st StreamId as 2147483641, the above loop takes around 4~5
seconds to execute and hence, the response is delayed.
Regards,
Prateek Kohli
-Original Message-
From: Manuel Dominguez Sarmiento
Sent: Thursday, May 21, 2020 3:34 PM
To: Tomcat Users List ; Prateek Kohli
Subject: Re: Http2 tomact server taking time in responding when 1st StreamId is
a large integer value like 2147483641
I must say that we're also seeing weird, seemingly random response delays from
Tomcat on HTTP/2 We haven't looked into it at such a low level though. We're
currently on
9.0.35 but we've been seeing this on previous versions as well.
*Manuel Dominguez Sarmiento*
On 21/05/2020 05:32, Prateek Kohli wrote:
>
> Hello,
>
> Tomcat version : 9.0.29
>
> We are running a Tomcat Http2 Server and a Jetty http2 client.
>
> When we send 1^st request from Jetty client to tomcat server with
> streamId number as 1, tomcat sends the WINDOW_UPDATE header and the
> response in 1~2 milliseconds.
>
> Packet number 164 is the response in the below tcpdump.
>
> But when we send the 1st request from jetty client to tomcat server
> with streamId as 2147483641, the 1^st response from tomcat comes after
> almost 5 seconds
>
> And the response for subsequent requests comes within 1~2 milliseconds.
>
> In the below tcpdump it can be seen that the response packet number
> 167 comes after almost 5 seconds from the tomcat server.
>
> Would you please be able to explain why the response from tomcat
> server is getting delayed when the 1^st StreamId number is a large
> integer i.e. 2147483641.
>
> Regards,
>
> Prateek Kohli
>
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Http2 tomact server taking time in responding when 1st StreamId is a large integer value like 2147483641
Hello, Tomcat version : 9.0.29 We are running a Tomcat Http2 Server and a Jetty http2 client. When we send 1st request from Jetty client to tomcat server with streamId number as 1, tomcat sends the WINDOW_UPDATE header and the response in 1~2 milliseconds. Packet number 164 is the response in the below tcpdump. [cid:image001.jpg@01D62F78.71F08F20] But when we send the 1st request from jetty client to tomcat server with streamId as 2147483641, the 1st response from tomcat comes after almost 5 seconds And the response for subsequent requests comes within 1~2 milliseconds. In the below tcpdump it can be seen that the response packet number 167 comes after almost 5 seconds from the tomcat server. [cid:image002.jpg@01D62F78.71F08F20] Would you please be able to explain why the response from tomcat server is getting delayed when the 1st StreamId number is a large integer i.e. 2147483641. Regards, Prateek Kohli
Problem in starting tomcat
Hi all, I am using following configuration: Java- jdk-11(EA) Tomcat- 8.5.31 OS: Red Hat Herby attaching log portion which indicating error: 09-Jul-2018 07:58:10.248 SEVERE [main] org.apache.tomcat.util.net.SSLUtilBase.getStore Failed to load keystore type [PKCS11] with path [/home/iseadminportal/.keystore] due to [PKCS11 not found] java.security.KeyStoreException: PKCS11 not found at java.base/java.security.KeyStore.getInstance(KeyStore.java:878) at org.apache.tomcat.util.net.SSLUtilBase.getStore(SSLUtilBase.java:125) at org.apache.tomcat.util.net.SSLHostConfigCertificate.getCertificateKeystore(SSLHostConfigCertificate.java:204) at org.apache.tomcat.util.net.jsse.IseJSSEUtil.getKeyManagers(IseJSSEUtil.java:174) at org.apache.tomcat.util.net.AbstractJsseEndpoint.createSSLContext(AbstractJsseEndpoint.java:114) at org.apache.tomcat.util.net.AbstractJsseEndpoint.initialiseSsl(AbstractJsseEndpoint.java:87) at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:225) at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1086) at org.apache.tomcat.util.net.AbstractJsseEndpoint.init(AbstractJsseEndpoint.java:268) at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:581) at org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:68) at org.apache.catalina.connector.Connector.initInternal(Connector.java:993) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107) at org.apache.catalina.core.StandardService.initInternal(StandardService.java:549) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107) at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:875) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107) at org.apache.catalina.startup.Catalina.load(Catalina.java:632) at org.apache.catalina.startup.Catalina.load(Catalina.java:655) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:309) at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:339) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:210) Caused by: java.security.NoSuchAlgorithmException: PKCS11 KeyStore not available at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:159) at java.base/java.security.Security.getImpl(Security.java:697) at java.base/java.security.KeyStore.getInstance(KeyStore.java:875) ... 29 more Due to this tomcat is stucking at initialization state. Can anyone help me Thanks Prateek
Errors in starting tomcat
Hi, I am having following configuration Java:JDK-11 Tomcat: 8.5.31 OS: RedHat I am getting following error: Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.xyz.PAPFacade at com.abc.NSFAdminUtil.getPAPFacade(NSFAdminUtil.java:93) at com.abc.NSFAdminUtil.getPAPFacade(NSFAdminUtil.java:86) at com.abc.NSFAdminServiceFactory.(NSFAdminServiceFactory.java:85) at com.abc. NSFAdminServiceFactory.getInstance(NSFAdminServiceFactory.java:107) at com.lmn.RemoteStorageClient.(RemoteStorageClient.java:43) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148) ... 103 more 05-Jul-2018 03:32:30.218 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file 05-Jul-2018 03:32:30.219 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/pxgrid] startup failed due to previous errors 05-Jul-2018 03:32:30.219 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Closing Spring root WebApplicationContext 05-Jul-2018 03:32:30.222 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/CSCOcpm/appsrv/apache-tomcat-8.5.31/pxgridwebapp/pxgrid] has finished in [7,471] ms 05-Jul-2018 03:32:30.223 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["https-jsse-nio2-8910"] 05-Jul-2018 03:32:30.224 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 51976 ms Daemon started successfully java_start done Waiting for a signal to be delivered create_tmp_file: /tmp/25518.jsvc_up -- It stucking at this point. When I am checking it status , it is showing “Initialization” state (remain at this state). Description about classes: PAPFacade class is present in some xyz.jar , NSFAdminUtil is in some abc jar. >From log we can say,“NSFAdminUtil.class” calling method of PAPFacade.class , >as it is giving error “NoClassDefFoundError” indicating that >NSFAdminUtil.class not able to find the path of class PAPFacade.class For resolving this I performed following thing: 1. In META-INF/MANIFEST.MF of abc.jar (jar where NSFAdminUtil.class is present) added “Class-Path: xyz.jar” (xyz.jar where PAPFacade.class is present) 2. In setenv.sh I put following line export CLASSPATH=/opt/apache-tomcat/apache-tomcat-8.5.31/lib/* (even check for *.jar also) Both these steps didn’t help me to resolve . Pls help me to figure out this problem. Thanks in advance. Regards Prateek
RE: problem in starting tomcat
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-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: problem in starting tomcat
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=0x7fd4f206e28a, pid=2412, tid=2412 > # > # JRE version: (11.0+18) (build ) > # > 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-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: problem in starting tomcat
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 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 < > ch...@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=0x7fd4f206e28a, 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-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > >
RE: problem in starting tomcat
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=0x7fd4f206e28a, 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-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: problem in starting tomcat
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 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 < > ch...@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=0x7fd4f206e28a, 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-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fd4f206e28a, 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 # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # --- S U M M A R Y Host: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz, 2 cores, 7G, Red Hat Enterprise Linux Server release 7.5 (Maipo) Time: Tue Jun 26 03:09:07 2018 UTC elapsed time: 0 seconds (0d 0h 0m 0s) --- T H R E A D --- Current thread (0x01491c70): JavaThread "Unknown thread" [_thread_in_vm, id=2412, stack(0x7fffbaa16000,0x7fffbab14000)] Stack: [0x7fffbaa16000,0x7fffbab14000], sp=0x7fffbab109b8, free space=1002k 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] C
Re: problem in starting tomcat
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 < ch...@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=0x7fd4f206e28a, 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-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
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=0x7fd4f206e28a, 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". 0x7fd4f23a441c 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
MyApp servlet not deploying
Hi, I was trying to run the "myapp" servlet example. The examples provided in the webapps directory seem to run fine but when i try the "myapp" example by deploying. compiling and so on as illustrated, I run into the following error: type Status report message /myapp/ description The requested resource (/myapp/) is not available. I checked up the logs and have no trace of any error. The web.xml is as follows: Hello, World Application This is a simple web application with a source code organization based on the recommendations of the Application Developer's Guide. HelloServlet mypackage.Hello HelloServlet /myapp I tried deploying using the front end and also by copying into "$CATALINA_HOME/webapps" but to no avail. When I log into the manager module, I lists this servlet but when i try viewing it as http://localhost:8080/myapp/ it gives me the above error. Please help me get my first servlet started with tomcat. By the way I am using Windows 2000. Thanks, Prateek - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
