Forums de discussion

Memory leak

Vadym Ivashyn, modifié il y a 10 années.

Memory leak

New Member Publications: 15 Date d'inscription: 05/07/13 Publications récentes
After deploy my portlet into liferay, I get message about memory leak.


15:38:42,570 INFO  [PortletHotDeployListener:512] 1 portlet for rigensis-web-cust-application-termination-term-deposit is available for use
15:38:42,573 INFO  [StartupListener:50] Context initialized for contextPath=[/rigensis-web-cust-application-termination-term-deposit]
15:38:42,620 INFO  [StartupListener:77] Copied input-editor.jsp from LiferayFaces JAR to context path file=[D:\work\git\rigensis-web\rigensis-web-portlets\rigensis-web-cust-application-termination-term-deposit\src\main\webapp\resources\liferay-ui\jsp\input-editor.jsp]
Oct 10, 2013 3:38:43 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error listenerStart
Oct 10, 2013 3:38:43 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/rigensis-web-cust-application-termination-term-deposit] startup failed due to previous errors
15:38:43,338 INFO  [PluginPackageUtil:1099] Reading plugin package for rigensis-web-cust-application-termination-term-deposit
15:38:43,339 WARN  [PluginPackageUtil:1058] Plugin package on context rigensis-web-cust-application-termination-term-deposit cannot be tracked because this WAR does not contain a liferay-plugin-package.xml file
15:38:43,346 INFO  [PortletHotDeployListener:549] Unregistering portlets for rigensis-web-cust-application-termination-term-deposit
15:38:43,356 INFO  [PortletHotDeployListener:580] 1 portlet for rigensis-web-cust-application-termination-term-deposit was unregistered
Oct 10, 2013 3:38:43 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/rigensis-web-cust-application-termination-term-deposit] created a ThreadLocal with key of type [com.sun.xml.bind.v2.ClassFactory$1] (value [com.sun.xml.bind.v2.ClassFactory$1@65665941]) and a value of type [java.util.WeakHashMap] (value [{class org.apache.camel.core.xml.CamelProxyFactoryDefinition=java.lang.ref.WeakReference@226dee69, class javax.xml.bind.annotation.adapters.CollapsedStringAdapter=java.lang.ref.WeakReference@5f3f4127, class org.apache.camel.spring.CamelContextFactoryBean=java.lang.ref.WeakReference@31ce984b, class java.util.ArrayList=java.lang.ref.WeakReference@72707d78}]) 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.


Why is it happened?
Can anybody help me?
thumbnail
David H Nebinger, modifié il y a 10 années.

RE: Memory leak

Liferay Legend Publications: 14919 Date d'inscription: 02/09/06 Publications récentes
Camel starts all kinds of background threads.

You must plug into the portlet destroy method to cleanly shut down your camel context objects.

You're getting the error because you have not cleanly shut camel down and those objects are lingering from the previous instance.
Vadym Ivashyn, modifié il y a 10 années.

RE: Memory leak

New Member Publications: 15 Date d'inscription: 05/07/13 Publications récentes
Thanks You for answer!

The problem is fixed.