RE: Java Heap Space Error
In Windows, the installer define Initial memory pool: 128 MB and Maximum memory pool: 256 MB, the configuration is available in the Tomcat8w gui app. I see the same on Tomcat 8 and 9. -Original Message- From: Christopher Schultz Sent: jueves, 20 de abril de 2023 09:21 a. m. To: users@tomcat.apache.org Subject: Re: Java Heap Space Error Pratik, On 4/20/23 03:35, pratik.kulka...@shell.com.INVALID wrote: > I guess you're right, Tomcat 9 allocates less default memory compared > to Tomcat 8; I checked our logs and below are the memory parameters > which seem to be passed in, > > Tomcat 9 - > > 14-Apr-2023 02:47:55.567 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Xms128m > 14-Apr-2023 02:47:55.567 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Xmx256m > > Tomcat 8 - > > 13-Apr-2023 06:10:01.520 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Xms512m > 13-Apr-2023 06:10:01.520 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Xmx1024m > > Like you suggested, I updated the configuration using Tomcat9w.exe since we > are running Tomcat as a service and it is now working without any errors! I > updated the sizes from 128MB and 256MB to 512MB and 1024MB respectively for > max and min pool sizes. > > Thank you very much everyone for your help, I truly appreciate it. I believe > we can mark this thread as solved. I don't believe Tomcat comes with any default at all. Whatever you are seeing there probably came from a local setup that you (or someone else local) did. Glad you got things working again. -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. La información transmitida está destinada únicamente a la persona o entidad a quien que va dirigida y puede contener información confidencial y/o material privilegiado. Cualquier revisión, retransmisión, difusión u otros usos, o cualquier acción tomada por personas o entidades distintas al destinatario basándose en esta información está prohibida. Si usted recibe este mensaje por error, por favor contacte al remitente y elimine el material de cualquier computadora. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 8.5 - Native Library - Crash
Any tips for building Tomcat Native on Windows 10? Best regards, Eduardo Quintanilla Software Developer Block Networks<http://www.blocknetworks.com.mx/> From: Christopher Schultz Sent: jueves, 22 de agosto de 2019 11:57 a. m. To: users@tomcat.apache.org Subject: Re: Tomcat 8.5 - Native Library - Crash Eduardo, On 8/22/19 10:18, Eduardo Quintanilla wrote: > Chris, > > The crash dump and logs[1] from my dev environment. > > [1]https://1drv.ms/u/s!AjSSUmqOgKmfi1g7z4wUvfYPksCk?e=CLH6VF Okay, as I suspected, it's a SIGSEGV, or what Java programmers would call a NullPointerException. The C code is computing a pointer with a 44 byte offset to a NULL pointer and trying to dereference it, which causes the problem. I'm not sure which field has a 44-byte offset into the structure it's supposed to be contained in. That highly depends upon the architecture, compiler, etc. and those are the things I don't have access to. If someone in the community is able to build tcnative for Windows in the same way[1] that the Tomcat team builds it, can you identify the following: 1. What line of code corresponds to tcnative-1.dll+0x14d32 2. Which structure is being used 3. Which field is 44 bytes into that structure Knowing all those things should make this a very easy fix. Of course, the "fix" will involve throwing an exception back over into the Java space, to the application will still throw an error. But at least it won't bring-down the whole JVM. >> Do you always get the "stream is not writable" error before the >> JVM performs the crash-dump? > > Yes but only in the Tomcat of the production environment. That's ... interesting. If Tomcat knows it can't write to the stream... why is it still writing to the stream? Note that the crash dump you posted is for an error in jni.Address.get() and not the one for Socket.sendb(). If you can generate a crash dump in Socket.sendb() that would be helpful, too. Also, please see: https://bz.apache.org/bugzilla/show_bug.cgi?id=62626 https://bz.apache.org/bugzilla/show_bug.cgi?id=63405 -chris > > Best regards, Eduardo Quintanilla Software Developer > > From: Christopher Schultz > mailto:ch...@christopherschultz.net>> Sent: > jueves, 22 de agosto de 2019 8:25 a. m. To: > users@tomcat.apache.org<mailto:users@tomcat.apache.org> Subject: Re: Tomcat > 8.5 - Native Library - > Crash > > > Eduardo, > > On 8/21/19 17:36, Eduardo Quintanilla wrote: >> We have been getting some crashes in Tomcat 8.5.43 lately. >> >> The environment is: * JDK 1.8.0_202 * Windows Server 2012 R2 >> >> The logs shows a tcnative exception. >> >> Crash Log: Current thread JavaThread >> "https-openssl-apr-8081-exec-298" daemon _thread_in_native Java >> frames: (J=compiled Java code, j=interpreted, Vv=VM code) J >> 15034 >> org.apache.tomcat.jni.Socket.sendb(JLjava/nio/ByteBuffer;II)I (0 >> bytes) @ 0x02962ddf [0x02962d80+0x5f] J 29164 C2 >> org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper.doWrite(ZLjav a > >> /nio/ByteBuffer;)V >> (242 bytes) @ 0x06d6933c [0x06d68b20+0x81c] J >> 27479 C2 org.apache.tomcat.util.net.SocketWrapperBase.flush(Z)Z >> (20 bytes) @ 0x053f6144 [0x053f60a0+0xa4] J 24666 >> C2 >> org.apache.coyote.http2.Http2OutputBuffer.doWrite(Ljava/nio/ByteBuffe r > >> ;)I >> (28 bytes) @ 0x06b51b74 [0x06b51660+0x514] J >> 24689 C2 >> org.apache.catalina.connector.OutputBuffer.writeBytes([BII)V (38 >> bytes) @ 0x031c09f8 [0x031c04c0+0x538] J 27348 >> C2 org.apache.catalina.connector.CoyoteOutputStream.write([BII)V >> (26 bytes) @ 0x071d51a8 [0x071d5120+0x88] > > What's the actual error? Can you post the entire crash dump? > >> Tomcat logs: org.apache.catalina.connector.ClientAbortException: >> org.apache.coyote.CloseNowException: Connection [214], Stream >> [279], This stream is not writable > > Do you always get the "stream is not writable" error before the > JVM performs the crash-dump? > > I believe there is at least one lingering SEGV hiding in > Socket.sendb(), possibly only on Windows. I don't have a Windows > development environment to be able to disassemble the crash dump > and locate the line of code being executed when the SEGV occurs, so > I have added NULL-checks to everything I can find in there but it > looks like it's not enough. Something is missing, somewhere. > > -chris > > > > The information transmitted is intended only for the person or > entity to which it is addressed and may contain confidential and/or > privileged material. Any review, retransmission, dissemination or > other use of, or taking
RE: Tomcat 8.5 - Native Library - Crash
Chris, The crash dump and logs[1] from my dev environment. [1]https://1drv.ms/u/s!AjSSUmqOgKmfi1g7z4wUvfYPksCk?e=CLH6VF > Do you always get the "stream is not writable" error before the JVM > performs the crash-dump? Yes but only in the Tomcat of the production environment. Best regards, Eduardo Quintanilla Software Developer From: Christopher Schultz Sent: jueves, 22 de agosto de 2019 8:25 a. m. To: users@tomcat.apache.org Subject: Re: Tomcat 8.5 - Native Library - Crash Eduardo, On 8/21/19 17:36, Eduardo Quintanilla wrote: > We have been getting some crashes in Tomcat 8.5.43 lately. > > The environment is: * JDK 1.8.0_202 * Windows Server 2012 R2 > > The logs shows a tcnative exception. > > Crash Log: Current thread JavaThread > "https-openssl-apr-8081-exec-298" daemon _thread_in_native Java > frames: (J=compiled Java code, j=interpreted, Vv=VM code) J 15034 > org.apache.tomcat.jni.Socket.sendb(JLjava/nio/ByteBuffer;II)I (0 > bytes) @ 0x02962ddf [0x02962d80+0x5f] J 29164 C2 > org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper.doWrite(ZLjava /nio/ByteBuffer;)V > (242 bytes) @ 0x06d6933c [0x06d68b20+0x81c] J 27479 > C2 org.apache.tomcat.util.net.SocketWrapperBase.flush(Z)Z (20 > bytes) @ 0x053f6144 [0x053f60a0+0xa4] J 24666 C2 > org.apache.coyote.http2.Http2OutputBuffer.doWrite(Ljava/nio/ByteBuffer ;)I > (28 bytes) @ 0x06b51b74 [0x06b51660+0x514] J 24689 > C2 org.apache.catalina.connector.OutputBuffer.writeBytes([BII)V (38 > bytes) @ 0x031c09f8 [0x031c04c0+0x538] J 27348 C2 > org.apache.catalina.connector.CoyoteOutputStream.write([BII)V (26 > bytes) @ 0x071d51a8 [0x071d5120+0x88] What's the actual error? Can you post the entire crash dump? > Tomcat logs: org.apache.catalina.connector.ClientAbortException: > org.apache.coyote.CloseNowException: Connection [214], Stream > [279], This stream is not writable Do you always get the "stream is not writable" error before the JVM performs the crash-dump? I believe there is at least one lingering SEGV hiding in Socket.sendb(), possibly only on Windows. I don't have a Windows development environment to be able to disassemble the crash dump and locate the line of code being executed when the SEGV occurs, so I have added NULL-checks to everything I can find in there but it looks like it's not enough. Something is missing, somewhere. -chris The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. La información transmitida está destinada únicamente a la persona o entidad a quien que va dirigida y puede contener información confidencial y/o material privilegiado. Cualquier revisión, retransmisión, difusión u otros usos, o cualquier acción tomada por personas o entidades distintas al destinatario basándose en esta información está prohibida. Si usted recibe este mensaje por error, por favor contacte al remitente y elimine el material de cualquier computadora.
RE: Tomcat 8.5 - Native Library - Crash
Tomcat Native versión 1.2.23.0, the included with Tomcat. Eduardo Quintanilla Software Developer -Original Message- From: Mark Thomas Sent: jueves, 22 de agosto de 2019 1:11 a. m. To: Tomcat Users List Subject: Re: Tomcat 8.5 - Native Library - Crash Tomcat Native version? Mark On August 21, 2019 9:36:44 PM UTC, Eduardo Quintanilla wrote: >We have been getting some crashes in Tomcat 8.5.43 lately. > >The environment is: >* JDK 1.8.0_202 >* Windows Server 2012 R2 > >The logs shows a tcnative exception. > >Crash Log: >Current thread JavaThread "https-openssl-apr-8081-exec-298" daemon >_thread_in_native Java frames: (J=compiled Java code, j=interpreted, >Vv=VM code) J 15034 >org.apache.tomcat.jni.Socket.sendb(JLjava/nio/ByteBuffer;II)I >(0 bytes) @ 0x02962ddf [0x02962d80+0x5f] J 29164 C2 >org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper.doWrite(ZLjava/ >nio/ByteBuffer;)V >(242 bytes) @ 0x06d6933c [0x06d68b20+0x81c] J 27479 C2 >org.apache.tomcat.util.net.SocketWrapperBase.flush(Z)Z (20 >bytes) @ 0x053f6144 [0x053f60a0+0xa4] J 24666 C2 >org.apache.coyote.http2.Http2OutputBuffer.doWrite(Ljava/nio/ByteBuffer; >)I >(28 bytes) @ 0x06b51b74 [0x06b51660+0x514] J 24689 C2 >org.apache.catalina.connector.OutputBuffer.writeBytes([BII)V >(38 bytes) @ 0x031c09f8 [0x031c04c0+0x538] J 27348 C2 >org.apache.catalina.connector.CoyoteOutputStream.write([BII)V (26 >bytes) @ 0x071d51a8 [0x071d5120+0x88] > >Tomcat logs: >org.apache.catalina.connector.ClientAbortException: >org.apache.coyote.CloseNowException: Connection [214], Stream [279], >This stream is not writable > > >I was able to cause a crash in my development environment but I do not >think that is the same error, I got the same error with version 9.0.24 >Sample app[1] Crash logs: >Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j >org.apache.tomcat.jni.Address.get(IJ)J+0 >j >org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper.populateRemoteA >ddr()V+21 >J 4645 C1 >org.apache.coyote.AbstractProcessor.action(Lorg/apache/coyote/ActionCod >e;Ljava/lang/Object;)V >(1019 bytes) @ 0x024a4774 [0x0249f700+0x5074] j >org.apache.coyote.Request.action(Lorg/apache/coyote/ActionCode;Ljava/la >ng/Object;)V+31 >j >org.apache.catalina.connector.Request.getRemoteAddr()Ljava/lang/String; >+18 >j >org.apache.catalina.connector.RequestFacade.getRemoteAddr()Ljava/lang/S >tring;+27 >j >org.springframework.web.servlet.FrameworkServlet.publishRequestHandledE >vent(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpSer >vletResponse;JLjava/lang/Throwable;)V+37 > > >Dev environment: >* Tomcat 8.5.43 >* Windows Server 2012 R2 >* Windows 10.0.18362.295 > >The keystore was created with: > >keytool -genkey -keyalg RSA -alias tomcat -keystore tomcat.jks >-storepass tomcat -validity 360 -keysize 2048 > > >The HTTPS connector is configured with: > >protocol="org.apache.coyote.http11.Http11AprProtocol" > maxThreads="150" SSLEnabled="true" > > > >certificateKeystorePassword="tomcat" certificateKeyPassword="tomcat" > type="RSA" /> > > > >I am running the tests with Gatling 3.2.0[3] configured with >requestTimeout = 60 so it causes client disconnections. >Sample test[2] > >The issue could be fixed in the app code but I think that is also a >Tomcat bug. >Any tipos or suggestions? > >[1][ >https://github.com/lalo-mx/app-tomcat-sample/blob/master/src/main/java/ >sample/AppController.java] [2][ >https://gist.github.com/lalo-mx/0a690290f6aac5017f15a65fc100eaa2] >[3][ https://gatling.io/open-source] > >Eduardo Quintanilla >Software Developer > > >The information transmitted is intended only for the person or entity >to which it is addressed and may contain confidential and/or privileged >material. Any review, retransmission, dissemination or other use of, or >taking of any action in reliance upon, this information by persons or >entities other than the intended recipient is prohibited. If you >received this in error, please contact the sender and delete the >material from any computer. >La información transmitida está destinada únicamente a la persona o >entidad a quien que va dirigida y puede contener información >confidencial y/o material privilegiado. Cualquier revisión, >retransmisión, difusión u otros usos, o cualquier acción tomada por >personas o entidades distintas al destinatario basándose en esta >información está prohibida. Si usted recibe este mensaje por error, p
Tomcat 8.5 - Native Library - Crash
We have been getting some crashes in Tomcat 8.5.43 lately. The environment is: * JDK 1.8.0_202 * Windows Server 2012 R2 The logs shows a tcnative exception. Crash Log: Current thread JavaThread "https-openssl-apr-8081-exec-298" daemon _thread_in_native Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) J 15034 org.apache.tomcat.jni.Socket.sendb(JLjava/nio/ByteBuffer;II)I (0 bytes) @ 0x02962ddf [0x02962d80+0x5f] J 29164 C2 org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper.doWrite(ZLjava/nio/ByteBuffer;)V (242 bytes) @ 0x06d6933c [0x06d68b20+0x81c] J 27479 C2 org.apache.tomcat.util.net.SocketWrapperBase.flush(Z)Z (20 bytes) @ 0x053f6144 [0x053f60a0+0xa4] J 24666 C2 org.apache.coyote.http2.Http2OutputBuffer.doWrite(Ljava/nio/ByteBuffer;)I (28 bytes) @ 0x06b51b74 [0x06b51660+0x514] J 24689 C2 org.apache.catalina.connector.OutputBuffer.writeBytes([BII)V (38 bytes) @ 0x031c09f8 [0x031c04c0+0x538] J 27348 C2 org.apache.catalina.connector.CoyoteOutputStream.write([BII)V (26 bytes) @ 0x071d51a8 [0x071d5120+0x88] Tomcat logs: org.apache.catalina.connector.ClientAbortException: org.apache.coyote.CloseNowException: Connection [214], Stream [279], This stream is not writable I was able to cause a crash in my development environment but I do not think that is the same error, I got the same error with version 9.0.24 Sample app[1] Crash logs: Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j org.apache.tomcat.jni.Address.get(IJ)J+0 j org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper.populateRemoteAddr()V+21 J 4645 C1 org.apache.coyote.AbstractProcessor.action(Lorg/apache/coyote/ActionCode;Ljava/lang/Object;)V (1019 bytes) @ 0x024a4774 [0x0249f700+0x5074] j org.apache.coyote.Request.action(Lorg/apache/coyote/ActionCode;Ljava/lang/Object;)V+31 j org.apache.catalina.connector.Request.getRemoteAddr()Ljava/lang/String;+18 j org.apache.catalina.connector.RequestFacade.getRemoteAddr()Ljava/lang/String;+27 j org.springframework.web.servlet.FrameworkServlet.publishRequestHandledEvent(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;JLjava/lang/Throwable;)V+37 Dev environment: * Tomcat 8.5.43 * Windows Server 2012 R2 * Windows 10.0.18362.295 The keystore was created with: keytool -genkey -keyalg RSA -alias tomcat -keystore tomcat.jks -storepass tomcat -validity 360 -keysize 2048 The HTTPS connector is configured with: I am running the tests with Gatling 3.2.0[3] configured with requestTimeout = 60 so it causes client disconnections. Sample test[2] The issue could be fixed in the app code but I think that is also a Tomcat bug. Any tipos or suggestions? [1][ https://github.com/lalo-mx/app-tomcat-sample/blob/master/src/main/java/sample/AppController.java] [2][ https://gist.github.com/lalo-mx/0a690290f6aac5017f15a65fc100eaa2] [3][ https://gatling.io/open-source] Eduardo Quintanilla Software Developer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. La información transmitida está destinada únicamente a la persona o entidad a quien que va dirigida y puede contener información confidencial y/o material privilegiado. Cualquier revisión, retransmisión, difusión u otros usos, o cualquier acción tomada por personas o entidades distintas al destinatario basándose en esta información está prohibida. Si usted recibe este mensaje por error, por favor contacte al remitente y elimine el material de cualquier computadora. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Help debugging stream error
Thanks Mark, I will keep the changelog in mind for future references. Eduardo Quintanilla Software Developer Block Networks -Original Message- From: Mark Thomas Sent: martes, 4 de diciembre de 2018 11:00 a. m. To: users@tomcat.apache.org Subject: Re: Help debugging stream error On 04/12/2018 15:24, Eduardo Quintanilla wrote: > Hi, > > I am having an sporadic error with our app that slows a lot the responses of > the server. > Any suggestions about how to find the cause of the error will be appreciated. > > Tomcat version: Apache Tomcat/8.5.20 > Java: JDK 1.8.0_191-b12 > VM Options: -Xms200m -Xmx7g -XX:PermSize=256m -XX:MaxPermSize=512m > -Drebel.always.rerun.clinit=true > -Dxwork.loggerFactory=com.opensymphony.xwork2.util.logging.slf4j.Slf4jLoggerFactory > -Dfile.encoding=UTF8 > -javaagent:"C:\equintanilla\Software\glowroot\glowroot.jar" > > Logs: > 04-Dec-2018 09:13:15.295 GRAVE [https-openssl-apr-9380-exec-123] > org.apache.coyote.AbstractProtocol$ConnectionHandler.process Error > reading request, ignored java.lang.StackOverflowError http://svn.apache.org/repos/asf/tomcat/tc8.5.x/trunk/webapps/docs/changelog.xml Search for "HTTP/2" or "StackOverflowError" The do the obvious to resolve the issue. Mark > at > java.util.Collections$SetFromMap.contains(Collections.java:5459) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:67) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71) > at > org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.jav > a:71) > > Connector: > protocol="org.apache.coyote.http11.Http11AprProtocol" > URIEncoding="UTF-8" maxThreads="150" > SSLEnabled="true" > > > > certificateFile="conf/localhost.cer" > type="RSA" /> > > > > > Eduardo Quintanilla > Software Developer > Block Networks<http://www.blocknetworks.com.mx/> > > - 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
Help debugging stream error
Hi,
I am having an sporadic error with our app that slows a lot the responses of
the server.
Any suggestions about how to find the cause of the error will be appreciated.
Tomcat version: Apache Tomcat/8.5.20
Java: JDK 1.8.0_191-b12
VM Options: -Xms200m -Xmx7g -XX:PermSize=256m -XX:MaxPermSize=512m
-Drebel.always.rerun.clinit=true
-Dxwork.loggerFactory=com.opensymphony.xwork2.util.logging.slf4j.Slf4jLoggerFactory
-Dfile.encoding=UTF8
-javaagent:"C:\equintanilla\Software\glowroot\glowroot.jar"
Logs:
04-Dec-2018 09:13:15.295 GRAVE [https-openssl-apr-9380-exec-123]
org.apache.coyote.AbstractProtocol$ConnectionHandler.process Error reading
request, ignored
java.lang.StackOverflowError
at
java.util.Collections$SetFromMap.contains(Collections.java:5459)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:67)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
at
org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:71)
Connector:
Eduardo Quintanilla
Software Developer
Block Networks<http://www.blocknetworks.com.mx/>
RE: [slightly OT] Re: Tomcat 9 does not work with Java 11
A follow up question. When the option "Use default" is selected in the Tomcatw manager. Where is that value configured? I assumed it was JAVA_HOME. Eduardo Quintanilla Software Developer Block Networks -Original Message- From: Mark Thomas Sent: martes, 27 de noviembre de 2018 4:23 a. m. To: users@tomcat.apache.org Subject: Re: [slightly OT] Re: Tomcat 9 does not work with Java 11 On 27/11/2018 08:47, André Warnier (tomcat) wrote: > On 27.11.2018 01:49, Christopher Schultz wrote: >> Hmm... just realized that the service.bat file might not be included >> in the "installer" bundle. You might have to grab the ZIP bundle from >> the Tomcat downloads site to get those scripts. >> >> - -chris > > This may be the right moment to suggest that this (these ?) ZIP > bundle(s) could be included by default, when running the installer > (not unpacked, just copied along and dropped somewhere). For as long > as I can remember (which is getting somewhat shorter these days, but > still goes back to tomcat 4.x), this has been an issue which regularly > crops up with the Windows versions : whenever something goes wrong, > people are being referred to files that they do not have, and it > always takes a while to explain, download etc.. > It would be easier if the files were already there anyway. > In the past, there may have been a concern for the extra size of the > download (nowadays about 11 MB for each 32/64 bit version), but > compared to many other downloads nowadays, this is still quite reasonable. > (And in fact, there are many common files, so not everything would > have to be downloaded. Also the 32-bit version is less useful these > days.) https://bz.apache.org/bugzilla/show_bug.cgi?id=56323 It wasn't back-ported to 7.0.x. I'm not aware of of causing issues in 8.5.x or 9.0.x so it could be back-ported. 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
