issue when upgrading from 1.6.5 to 1.7.2

125 views

Skip to first unread message

Franck Lamberton

unread,

Jan 17, 2017, 6:58:07 PM1/17/17

to xnat_discussion

Hi all

I used the default version of XNAT (without any customizations) for 3 years, upgrading successively to 1.6.3, 1.6.4 and 1.6.5. I've just tried to upgrade to 1.7.2 and it seems that something is blocked during the initialization.

After upgrading, I can open the 1st page of XNAT in Firefox (launch from the VM to be able to access to XNAT server with the address localhost, password for admin as well as a user are recognized (in ${xnat.home}/logs/access.log, lines are terminated by "Authentication SUCCESS") but I never manage to reach the rest of XNAT. The message in Firefox is :

The page isn't redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

This problem can sometimes be caused by disabling or refusing to accept cookies.

and if check ${xnat.home}/logs/security.log, I've these lines :

...
2017-01-17 21:24:21,172 [http-bio-8080-exec-2] WARN org.nrg.xnat.security.XnatInitCheckFilter - Admin user admin has logged into the uninitialized server and is being redirected to http://localhost:8080/xnat/setup
2017-01-17 23:35:27,975 [http-bio-8080-exec-7] WARN org.nrg.xnat.security.XnatInitCheckFilter - Non-admin user franck has logged into the uninitialized server and is being redirected to http://localhost:8080/xnat/app/template/Unconfigured.vm
...

I can reinstall the copy of XNAT 1.6.5 in /var/lib/tomcat7/webapps and remove the value xnat.home from JAVA_OPTS in /etc/default/tomcat7 and everything works fine.

Have you any idea about what's going wrong ?

If needed, my configuration (didn't change from my 1st installation of 1.6.2), the XNAT server runs in a VM (up to date Debian 7 with the default tomcat7, JDK 1.7 and postgresql 9.1). Tomcat7 is running under the account "xnat" account ($HOME is /home/xnat).

The data are stored in the host of the server, in the directory /data/XNAT, this is locally exported to the VM by NFS. the account XNAT have read/write access to the data in the VM.

To upgrade to 1.7.2, I follow the explanations : https://wiki.xnat.org/documentation/getting-started-with-xnat-1-7/upgrading-to-xnat-1-7-from-an-earlier-version

I define xnat.home as /home/xnat/xnat-1.7.2 as I prefer to keep this part in the VM if it's possible.

The configuration file xnat-conf.properties was the same as the default version, except the password to access to the database.

In order to keep the same URL that I already use, I copy the xnat-web-1.7.2.war file in /var/lib/tomcat7/webapps/xnat.war.

During the 1st start of Tomcat I had these lines in /var/lib/tomcat7/catalina.out :

...
GRAVE: Error waiting for multi-thread deployment of WAR files to complete
java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Java heap space
...

GRAVE: SEVERE:Memory usage is low, parachute is non existent, your system may start failing.
...

I changed JAVA_OPTS in /etc/default/tomcat7, from

JAVA_OPTS="-Djava.awt.headless=true -Xms512m -Xmx1024m -XX:+UseConcMarkSweepGC"

JAVA_OPTS="-Djava.awt.headless=true -Xms512m -Xmx2g -XX:+UseConcMarkSweepGC"

The error message about memory disappeared but java took the 2G of allowed memory (the VM has 3G) )and never release them as checked with top :

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8490 xnat 20 0 2760m 1,8g 14m S 0,7 63,8 6:30.44 java
...

This doesn't occur with XNAT 1.6.5 ???

I also copy/paste below the /var/log/tomcat7/catalina.out

janv. 17, 2017 1:03:11 PM org.apache.catalina.core.StandardService startInternal
INFOS: D�marrage du service Catalina
janv. 17, 2017 1:03:11 PM org.apache.catalina.core.StandardEngine startInternal
INFOS: Starting Servlet Engine: Apache Tomcat/7.0.28
janv. 17, 2017 1:03:11 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFOS: D�ploiement du descripteur de configuration /etc/tomcat7/Catalina/localhost/host-manager.xml
janv. 17, 2017 1:03:12 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFOS: D�ploiement du descripteur de configuration /etc/tomcat7/Catalina/localhost/manager.xml
janv. 17, 2017 1:03:12 PM org.apache.catalina.startup.HostConfig deployWAR
INFOS: D�ploiement de l'archive /var/lib/tomcat7/webapps/xnat.war de l'application web
janv. 17, 2017 1:04:19 PM org.apache.catalina.session.StandardManager doLoad
GRAVE: "ClassNotFoundException" lors du chargement de sessions persistantes: java.lang.ClassNotFoundException: net.bull.javamelody.SessionListener
java.lang.ClassNotFoundException: net.bull.javamelody.SessionListener
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:278)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:628)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1521)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1779)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:373)
at org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1595)
at org.apache.catalina.session.StandardSession.readObjectData(StandardSession.java:1060)
at org.apache.catalina.session.StandardManager.doLoad(StandardManager.java:287)
at org.apache.catalina.session.StandardManager.load(StandardManager.java:204)
at org.apache.catalina.session.StandardManager.startInternal(StandardManager.java:494)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5330)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:618)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:963)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1600)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

janv. 17, 2017 1:04:20 PM org.apache.catalina.session.StandardManager startInternal
GRAVE: Exception au chargement des sessions depuis le stockage persistant (persistent storage)
java.lang.ClassNotFoundException: net.bull.javamelody.SessionListener
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:278)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:628)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1521)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1779)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:373)
at org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1595)
at org.apache.catalina.session.StandardSession.readObjectData(StandardSession.java:1060)
at org.apache.catalina.session.StandardManager.doLoad(StandardManager.java:287)
at org.apache.catalina.session.StandardManager.load(StandardManager.java:204)
at org.apache.catalina.session.StandardManager.startInternal(StandardManager.java:494)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5330)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:618)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:963)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1600)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

SOURCE: /var/lib/tomcat7/webapps/xnat/
Database up to date.
janv. 17, 2017 1:04:42 PM org.apache.catalina.startup.HostConfig deployDirectory
INFOS: D�ploiement du r�pertoire /var/lib/tomcat7/webapps/ROOT de l'application web
janv. 17, 2017 1:04:43 PM org.apache.coyote.AbstractProtocol start
INFOS: Starting ProtocolHandler ["http-bio-8080"]
janv. 17, 2017 1:04:43 PM org.apache.coyote.AbstractProtocol start
INFOS: Starting ProtocolHandler ["http-nio-8443"]
janv. 17, 2017 1:04:43 PM org.apache.catalina.startup.Catalina start
INFOS: Server startup in 92205 ms
janv. 18, 2017 12:29:22 AM org.apache.coyote.AbstractProtocol pause
INFOS: Pausing ProtocolHandler ["http-bio-8080"]
janv. 18, 2017 12:29:23 AM org.apache.coyote.AbstractProtocol pause
INFOS: Pausing ProtocolHandler ["http-nio-8443"]
janv. 18, 2017 12:29:23 AM org.apache.catalina.core.StandardService stopInternal
INFOS: Arr�t du service Catalina
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
GRAVE: The web application [/xnat] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [pool-2-thread-1] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ BrokerService[activeMQBroker] Task-25] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_QuartzSchedulerThread] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.python.core.ThreadStateMapping$1] (value [org.python.core.ThreadStateMapping$1@3f56821d]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@48785e67]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.connector=vm://localhost}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.coyote.AbstractProtocol stop
INFOS: Stopping ProtocolHandler ["http-bio-8080"]
janv. 18, 2017 12:29:40 AM org.apache.coyote.AbstractProtocol stop
INFOS: Stopping ProtocolHandler ["http-nio-8443"]
janv. 18, 2017 12:29:41 AM org.apache.coyote.AbstractProtocol destroy
INFOS: Destroying ProtocolHandler ["http-bio-8080"]
janv. 18, 2017 12:29:41 AM org.apache.coyote.AbstractProtocol destroy
INFOS: Destroying ProtocolHandler ["http-nio-8443"]
root@primage-xnat-int:/var/lib/tomcat7/webapps# cat /var/log/tomcat7/catalina.
catalina.2017-01-14.log catalina.out.13.gz catalina.out.21.gz catalina.out.2.gz catalina.out.38.gz catalina.out.46.gz catalina.out.6.gz
catalina.2017-01-15.log catalina.out.14.gz catalina.out.22.gz catalina.out.30.gz catalina.out.39.gz catalina.out.47.gz catalina.out.7.gz
catalina.2017-01-16.log catalina.out.15.gz catalina.out.23.gz catalina.out.31.gz catalina.out.3.gz catalina.out.48.gz catalina.out.8.gz
catalina.2017-01-17.log catalina.out.16.gz catalina.out.24.gz catalina.out.32.gz catalina.out.40.gz catalina.out.49.gz catalina.out.9.gz
catalina.2017-01-18.log catalina.out.17.gz catalina.out.25.gz catalina.out.33.gz catalina.out.41.gz catalina.out.4.gz
catalina.out catalina.out.18.gz catalina.out.26.gz catalina.out.34.gz catalina.out.42.gz catalina.out.50.gz
catalina.out.10.gz catalina.out.19.gz catalina.out.27.gz catalina.out.35.gz catalina.out.43.gz catalina.out.51.gz
catalina.out.11.gz catalina.out.1.gz catalina.out.28.gz catalina.out.36.gz catalina.out.44.gz catalina.out.52.gz
catalina.out.12.gz catalina.out.20.gz catalina.out.29.gz catalina.out.37.gz catalina.out.45.gz catalina.out.5.gz
root@primage-xnat-int:/var/lib/tomcat7/webapps# cat /var/log/tomcat7/catalina.2017-01-18.log
janv. 18, 2017 12:29:22 AM org.apache.coyote.AbstractProtocol pause
INFOS: Pausing ProtocolHandler ["http-bio-8080"]
janv. 18, 2017 12:29:23 AM org.apache.coyote.AbstractProtocol pause
INFOS: Pausing ProtocolHandler ["http-nio-8443"]
janv. 18, 2017 12:29:23 AM org.apache.catalina.core.StandardService stopInternal
INFOS: Arr�t du service Catalina
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
GRAVE: The web application [/xnat] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [pool-2-thread-1] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [ActiveMQ BrokerService[activeMQBroker] Task-25] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/xnat] appears to have started a thread named [DefaultQuartzScheduler_QuartzSchedulerThread] but has failed to stop it. This is very likely to create a memory leak.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.python.core.ThreadStateMapping$1] (value [org.python.core.ThreadStateMapping$1@3f56821d]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@48785e67]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [/xnat] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@567de15c]) and a value of type [java.util.Hashtable] (value [{activemq.connector=vm://localhost}]) 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.
janv. 18, 2017 12:29:40 AM org.apache.coyote.AbstractProtocol stop
INFOS: Stopping ProtocolHandler ["http-bio-8080"]
janv. 18, 2017 12:29:40 AM org.apache.coyote.AbstractProtocol stop
INFOS: Stopping ProtocolHandler ["http-nio-8443"]
janv. 18, 2017 12:29:41 AM org.apache.coyote.AbstractProtocol destroy
INFOS: Destroying ProtocolHandler ["http-bio-8080"]
janv. 18, 2017 12:29:41 AM org.apache.coyote.AbstractProtocol destroy
INFOS: Destroying ProtocolHandler ["http-nio-8443"]

Herrick, Rick

unread,

Jan 18, 2017, 3:26:14 PM1/18/17

to xnat_di...@googlegroups.com

That definitely looks like something abnormal going on. The most disturbing thing is this:

java.lang.ClassNotFoundException: net.bull.javamelody.SessionListener

Not because that’s such an important class but because that class is definitely in the 1.7.2 build:

$ jar xf xnat-web-1.7.2.war WEB-INF/lib/javamelody-core-1.58.0.jar

$ jar tf WEB-INF/lib/javamelody-core-1.58.0.jar| grep net.bull.javamelody.SessionListener

net/bull/javamelody/SessionListener$SessionInformationsComparator.class

net/bull/javamelody/SessionListener.class

Maybe you have multiple versions of the application installed? What makes me think that is this:

SOURCE: /var/lib/tomcat7/webapps/xnat/

Database up to date.

janv. 17, 2017 1:04:42 PM org.apache.catalina.startup.HostConfig deployDirectory

INFOS: D�ploiement du r�pertoire /var/lib/tomcat7/webapps/ROOT

If you had two versions of XNAT installed, that can cause a lot of problems. What’s in your webapps folder?

Rick Herrick

Sr. Programmer/Analyst

Neuroinformatics Research Group

Washington University School of Medicine

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To post to this group, send email to xnat_di...@googlegroups.com.
Visit this group at https://groups.google.com/group/xnat_discussion.
For more options, visit https://groups.google.com/d/optout.

The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.

Franck Lamberton

unread,

Jan 21, 2017, 6:43:46 AM1/21/17

to xnat_discussion

I performed different tests and I think to have find a workaround in my case : XNAT-1.7.2 must be installed as ROOT.war. I still to test to archive some data next week.

I double check, the ROOT directory was the default ROOT directory created I suppose during the installation of Tomcat. I kept it when I installed XNAT 1.6.X.

tree -pugshQ /var/lib/tomcat7/webapps/ROOT/
"ROOT/"
├── [-rw-r--r-- xnat xnat 1.9K] "index.html"
└── [drwxr-xr-x xnat xnat 4.0K] "META-INF"
└── [-rw-r--r-- xnat xnat 51] "context.xml"

cat /var/lib/tomcat7/webapps/ROOT/index.html :

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Apache Tomcat</title>
</head>

<body>
<h1>It works !</h1>

<p>If you're seeing this page via a web browser, it means you've setup Tomcat successfully. Congratulations!</p>

<p>This is the default Tomcat home page. It can be found on the local filesystem at: <code>/var/lib/tomcat7/webapps/ROOT/index.html</code></p>
...

<p>NOTE: For security reasons, using the manager webapp is restricted to users with role "manager-gui". The host-manager webapp is restricted to users with role "admin-gui". Users are defined in <code>/etc/tomcat7/tomcat-users.xml</code>.</p>

</body>
</html>

So, I restarted from my working VM with XNAT 1.6.5. This time, I also upgraded Postgresql from 9.1 to 9.6 but this doesn't change the behavior :

* -Xmx=1g is not sufficient, increasing to 2g, I've no error and java never free all the available memory (I don't if it's important).

* During all my tests, the first time I start tomcat7 with xnat-1.7.2, the database was correctly updated if needed (no error message in catalina.out).

* Copying the .war as /var/lib/tomcat7/webapps/xnat.war lead to the same result (1st page available, login authorized as proved by access.log but error in redirection after).

* Deleting the directory (before or after) ROOT didn't change anything.

${xnat.home}/logs/jms.log is updated with :

2017-01-21 12:08:45,788 Established shared JMS Connection: ActiveMQConnection {id=ID:primage-xnat-int.XXX.YYY.ZZZ-33916-1484996924600-3:1,clientId=null,started=false}
2017-01-21 12:14:10,700 Encountered a JMSException - resetting the underlying JMS Connection
javax.jms.JMSException: Broker has been stopped: org.apache.activemq.broker.BrokerService$5@4a989723
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1949)
at org.apache.activemq.ActiveMQConnection$3$1.run(ActiveMQConnection.java:1869)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Caused by: org.apache.activemq.broker.BrokerStoppedException: Broker has been stopped: org.apache.activemq.broker.BrokerService$5@4a989723
at org.apache.activemq.broker.ErrorBroker.getBrokerService(ErrorBroker.java:252)
at org.apache.activemq.broker.MutableBrokerFilter.getBrokerService(MutableBrokerFilter.java:261)
at org.apache.activemq.broker.region.Queue.isSlave(Queue.java:1712)
at org.apache.activemq.broker.region.Queue.removeSubscription(Queue.java:583)
at org.apache.activemq.broker.region.AbstractRegion.removeConsumer(AbstractRegion.java:381)
at org.apache.activemq.broker.region.RegionBroker.removeConsumer(RegionBroker.java:445)
at org.apache.activemq.broker.BrokerFilter.removeConsumer(BrokerFilter.java:117)
at org.apache.activemq.advisory.AdvisoryBroker.removeConsumer(AdvisoryBroker.java:254)
at org.apache.activemq.broker.BrokerFilter.removeConsumer(BrokerFilter.java:117)
at org.apache.activemq.broker.BrokerFilter.removeConsumer(BrokerFilter.java:117)
at org.apache.activemq.broker.MutableBrokerFilter.removeConsumer(MutableBrokerFilter.java:123)
at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:76)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:294)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:152)
at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:241)
at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
... 3 more

* However, copying the .war file as ROOT.war, and deleting in this case everything included the directory ROOT lead to a operational XNAT server. This time, I manage to obtain the web of the server and was able to move in the different tab, check the site administration tab and send email.

So, in my case, XNAT 1.7.2 seems to work only when installed as ROOT.

However, I still observe an error message about net.bull.javamelody.SessionListener. I copy/paste below the content of catalina.out corresponding to a full cycle of start / stop of tomcat7 (so with XNAT installed as ROOT), could you check this and maybe give some suggestions about where to explore further ?

...

janv. 21, 2017 11:56:58 AM org.apache.coyote.AbstractProtocol init
INFOS: Initializing ProtocolHandler ["http-bio-8080"]
janv. 21, 2017 11:56:58 AM org.apache.coyote.AbstractProtocol init
INFOS: Initializing ProtocolHandler ["http-nio-8443"]
janv. 21, 2017 11:56:59 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFOS: Using a shared selector for servlet write/read
janv. 21, 2017 11:56:59 AM org.apache.catalina.startup.Catalina load
INFOS: Initialization processed in 1718 ms
janv. 21, 2017 11:56:59 AM org.apache.catalina.core.StandardService startInternal

INFOS: D�marrage du service Catalina

janv. 21, 2017 11:56:59 AM org.apache.catalina.core.StandardEngine startInternal

INFOS: Starting Servlet Engine: Apache Tomcat/7.0.28

janv. 21, 2017 11:56:59 AM org.apache.catalina.startup.HostConfig deployDescriptor

INFOS: D�ploiement du descripteur de configuration /etc/tomcat7/Catalina/localhost/host-manager.xml

janv. 21, 2017 11:56:59 AM org.apache.catalina.startup.HostConfig deployDescriptor

INFOS: D�ploiement du descripteur de configuration /etc/tomcat7/Catalina/localhost/manager.xml

janv. 21, 2017 11:57:00 AM org.apache.catalina.startup.HostConfig deployWAR
INFOS: D�ploiement de l'archive /var/lib/tomcat7/webapps/ROOT.war de l'application web
janv. 21, 2017 11:58:02 AM org.apache.catalina.session.StandardManager doLoad

janv. 21, 2017 11:58:02 AM org.apache.catalina.session.StandardManager startInternal

SOURCE: /var/lib/tomcat7/webapps/ROOT/
Database up to date.
janv. 21, 2017 11:58:19 AM org.apache.coyote.AbstractProtocol start
INFOS: Starting ProtocolHandler ["http-bio-8080"]
janv. 21, 2017 11:58:19 AM org.apache.coyote.AbstractProtocol start
INFOS: Starting ProtocolHandler ["http-nio-8443"]
janv. 21, 2017 11:58:19 AM org.apache.catalina.startup.Catalina start
INFOS: Server startup in 80393 ms
janv. 21, 2017 11:59:55 AM org.apache.coyote.AbstractProtocol pause
INFOS: Pausing ProtocolHandler ["http-bio-8080"]
janv. 21, 2017 11:59:55 AM org.apache.coyote.AbstractProtocol pause
INFOS: Pausing ProtocolHandler ["http-nio-8443"]
janv. 21, 2017 11:59:55 AM org.apache.catalina.core.StandardService stopInternal

INFOS: Arr�t du service Catalina

janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
GRAVE: The web application [] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [ActiveMQ Cleanup Timer] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [DefaultQuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [DefaultQuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [DefaultQuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [DefaultQuartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [DefaultQuartzScheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [DefaultQuartzScheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [DefaultQuartzScheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [DefaultQuartzScheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [DefaultQuartzScheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [pool-2-thread-1] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [ActiveMQ BrokerService[activeMQBroker] Task-7] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [] appears to have started a thread named [DefaultQuartzScheduler_QuartzSchedulerThread] but has failed to stop it. This is very likely to create a memory leak.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [] created a ThreadLocal with key of type [org.python.core.ThreadStateMapping$1] (value [org.python.core.ThreadStateMapping$1@135d7d37]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@5ec7afcf]) 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.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@7e76fa6]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@7e76fa6]) and a value of type [java.util.Hashtable] (value [{activemq.broker=activeMQBroker}]) 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.
janv. 21, 2017 12:00:13 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
GRAVE: The web application [] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@7e76fa6]) and a value of type [java.util.Hashtable] (value [{activemq.connector=vm://localhost}]) 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.
janv. 21, 2017 12:00:13 PM org.apache.coyote.AbstractProtocol stop
INFOS: Stopping ProtocolHandler ["http-bio-8080"]
janv. 21, 2017 12:00:13 PM org.apache.coyote.AbstractProtocol stop
INFOS: Stopping ProtocolHandler ["http-nio-8443"]
janv. 21, 2017 12:00:13 PM org.apache.coyote.AbstractProtocol destroy
INFOS: Destroying ProtocolHandler ["http-bio-8080"]
janv. 21, 2017 12:00:13 PM org.apache.coyote.AbstractProtocol destroy
INFOS: Destroying ProtocolHandler ["http-nio-8443"]

Thanks in advance.

Franck

Reply all

Reply to author

Forward

0 new messages