After upgrading Lucee to latest, I keep getting Lucee crashes with GC overhead limit exceeded. Haven’t changed my app so wondering if there’s a memory leak in Lucee causing this? Unfortunately, there aren’t any errors in Lucee logs except for above and what’s shown below for application.log. Catalina log is also included.
Anyone else encountering issues? Any thoughts on how to debug?
Thanks.
Version Lucee 5.2.3.35
Version Name Velvet
Release date Sep 1, 2017
ColdFusion® compatibility version 2016.0.03.300357
Configuration File /opt/lucee/tomcat/lucee-server/context/lucee-server.xml
OS Linux (3.2.0-4-amd64) 64bit
Remote IP 134.174.91.51
Host Name orrms2.bwhanesthesia.org
Servlet Container Apache Tomcat/8.5.6
Java 1.8.0_112 (Oracle Corporation) 64bit
Architecture 64bit
application.log
"ERROR","http-nio-8888-exec-15","09/14/2017","17:14:26","",";"
"ERROR","http-nio-8888-exec-16","09/14/2017","17:14:31","",";"
"ERROR","http-nio-8888-exec-16","09/14/2017","17:15:08","",";"
"ERROR","http-nio-8888-exec-8","09/14/2017","17:15:11","",";"
"ERROR","http-nio-8888-exec-20","09/14/2017","17:15:13","",";"
"ERROR","http-nio-8888-exec-5","09/14/2017","17:15:54","",";"
"ERROR","http-nio-8888-exec-12","09/14/2017","17:16:02","",";"
"ERROR","http-nio-8888-exec-12","09/14/2017","17:16:02","",";"
"ERROR","http-nio-8888-exec-18","09/14/2017","17:21:44","",";"
"ERROR","http-nio-8888-exec-9","09/14/2017","17:22:24","",";"
"ERROR","http-nio-8888-exec-7","09/14/2017","17:22:27","",";"
"ERROR","http-nio-8888-exec-20","09/14/2017","17:22:29","",";"
catalina.log
13-Sep-2017 10:20:22.205 WARNING [127.0.0.1-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have st
arted a thread named [FelixFrameworkWiring] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:502)
org.apache.felix.framework.FrameworkWiringImpl.run(FrameworkWiringImpl.java:172)
java.lang.Thread.run(Thread.java:745)
13-Sep-2017 10:20:22.206 WARNING [127.0.0.1-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have st
arted a thread named [FelixStartLevel] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:502)
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:283)
java.lang.Thread.run(Thread.java:745)
13-Sep-2017 10:20:22.220 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-8888"]
13-Sep-2017 10:20:22.397 SEVERE [http-nio-8888-exec-59] org.apache.coyote.http11.Http11Processor.service Error processing request
java.lang.NullPointerException
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:389)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:784)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:802)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1410)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
13-Sep-2017 10:20:22.400 SEVERE [http-nio-8888-exec-59] org.apache.coyote.http11.Http11Processor.endRequest Error finishing response
java.lang.NullPointerException
at org.apache.coyote.http11.Http11OutputBuffer.flushBuffer(Http11OutputBuffer.java:514)
at org.apache.coyote.http11.Http11OutputBuffer.finishResponse(Http11OutputBuffer.java:301)
at org.apache.coyote.http11.Http11Processor.endRequest(Http11Processor.java:1459)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:824)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:802)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1410)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
13-Sep-2017 10:20:27.229 WARNING [main] org.apache.tomcat.util.net.AbstractEndpoint.shutdownExecutor The executor associated with thread pool [http-nio-8888] has not fully sh
utdown. Some application threads may still be running.