nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Alfresco created a ThreadLocal but failed remove it on stop

othlen

Hi,

in my tomcat log i found this SEVERE note:

SEVERE: The web application [/alfresco] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@6ac42579]) and a value of type [null] (value [org.alfresco.web.bean.NavigationBean$2@16ca6613]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
Dec 17, 2010 9:22:29 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
‍‍‍‍

Moreover when i try to start and stop alfresco, at third or forth time alfresco don't start for

 java.lang.OutOfMemoryError: PermGen space ‍

.

Someone can solve it?

Find more posts tagged with

Comments

mrogers

You can ignore the ThreadLocal stuff - Tomcat is being too pedantic.

For your second error, You need to increase the permgen space available to Alfresco.

Here's my dev settings which may be far too small, however you can tweak the numbers for -Xmx and -XX

ermSize upwards.
e.g.
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx1024m -Xss96k -server -XX

ermSize=300m -Duser.language=us -Duser.country=US

othlen

Thanks for your reply.

You can ignore the ThreadLocal stuff - Tomcat is being too pedantic.

Ignoring SEVERE signals is a good idea if you are quite sure that they are not caused by something real.
Our problem is, however, real: when we close and reopen alfresco 3 times the exception always happens.

For your second error, You need to increase the permgen space available to Alfresco.

IMHO the second error is dependent on the first one, so increasing the heap size (that is 4Gb already) can only make our system work some more time, but the issue is still there and is not solved.