tyson.decker Posted April 5, 2016 Posted April 5, 2016 I'm running jasperserver v6.0.1 and i'm having issues when trying to shutdown tomcat. I did not install the bundled tomcat, I installed using the js-install.sh script. Occasionally we need to shutdown tomcat to do some maintenance. It doesn't shutdown all the way and we end up having multiple zombie tomcat intances running.Looking in the logs I see several SEVERE warnings saying theres a probable memory leak.SEVERE: The web application [/jasperserver-pro] created a ThreadLocal with key of type [java.lang.InheritableThreadLocal] (value [java.lang.InheritableThreadLocal@21671cf3]) and a value of type [org.springframework.security.authentication.UsernamePasswordAuthenticationToken] (value [org.springframework.security.authentication.UsernamePasswordAuthenticationToken@8eb2e32c: Principal: MetadataUserDetails: hardy; Credentials: [PROTECTED]; Authenticated: true; Details: null; Granted Authorities: com.jaspersoft.jasperserver.api.metadata.user.domain.impl.client.TenantAwareGrantedAuthority@2a86d03SEVERE: The web application [/jasperserver-pro] created a ThreadLocal with key of type [java.lang.InheritableThreadLocal] (value [java.lang.InheritableThreadLocal@789da6a6]) and a value of type [com.jaspersoft.jasperserver.multipleTenancy.TenantContext] (value [Multitenancy context: organization 373]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.SEVERE: The web application [/jasperserver-pro] created a ThreadLocal with key of type [java.lang.InheritableThreadLocal] (value [java.lang.InheritableThreadLocal@185d03dc]) and a value of type [org.springframework.security.core.context.SecurityContextImpl] (value [org.springframework.security.core.context.SecurityContextImpl@ffffffff: Null authentication]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.There are several other errors, they seem to mostly be related to authentication. This basically happens everytime I try to shutdown tomcat. I also tried a clean install of jasperserver-pro 6.2.0 without any configuration changes. The only thing I did was import my current reports. I ran into the same issue of tomcat not shutting down. I've exhausted all of my resources and can't figure out why this is happening.Has anybody else experienced a simmilar issue and might know how to solve this?
hozawa Posted April 6, 2016 Posted April 6, 2016 No. The memory error happens but shouldn't be the cause of tomcat not shutting down. Check if the server shutdown properly without JasperReports Server war. Next, JasperReports Server install but without any modification nor resource added.I also recommend version up to 6.2.0. 6.0.1 was unstable and I passed it up. 6.1.x was more stable.
tyson.decker Posted April 6, 2016 Author Posted April 6, 2016 Wihtout the JasperReports Server war tomcat shuts down properly. With a clean install of 6.2.0 and no modifications or resources added tomcat will not shutdown. I'm installing it on CentOS using tomcat7. After trying to shutdown the memory errors are thrown and tomcat never quits. typing `ps aux` shows a tomcat process still runningtomcat 15008 7.4 10.0 6931780 810292 ? Sl 12:32 3:09 /usr/bin/java -Djava.util.logging.config.file=/usr/share/tomcat7/conf/logging.properties.... Trying to startup tomcat again results in multiple instances of tomcat running so I need to manually kill the process everytime.
jacob.li Posted August 18, 2017 Posted August 18, 2017 hozawa,Are the severe messages are expected when Tomcat shuts down? I see these get logged too (albeit no shutdown issue for me).
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now