Eliminare memory leak Alfresco su Tomcat

[koopa]

Ciao a tutti,
dopo una corretta installazione di Alfresco + Share su Tomcat 7 noto che, stoppando il server con lo script di shutdown, Tomcat rimane appeso e sono costretto a killare il processo che lo tiene in vita. Dai log di catalina noto che alfresco non riesce a stoppare dei thread creati da lui. E' possibile risolvere?
Queste le righe interessanti del log:

mag 22, 2012 2:17:08 PM org.apache.catalina.core.StandardService stopInternal
Informazioni: Stopping service Catalina
mag 22, 2012 2:17:11 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/alfresco] appears to have started a thread named [SolrWatcherScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
mag 22, 2012 2:17:11 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/alfresco] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
mag 22, 2012 2:17:11 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/alfresco] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak.
mag 22, 2012 2:17:11 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/alfresco] appears to have started a thread named [Timer-3] but has failed to stop it. This is very likely to create a memory leak.
mag 22, 2012 2:17:11 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/alfresco] appears to have started a thread named [Timer-4] but has failed to stop it. This is very likely to create a memory leak.
mag 22, 2012 2:17:11 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/alfresco] appears to have started a thread named [Timer-5] but has failed to stop it. This is very likely to create a memory leak.
mag 22, 2012 2:17:11 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/alfresco] appears to have started a thread named [Timer-6] but has failed to stop it. This is very likely to create a memory leak.
mag 22, 2012 2:17:11 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/alfresco] appears to have started a thread named [Win32HostAnnouncer_L0] but has failed to stop it. This is very likely to create a memory leak.
mag 22, 2012 2:17:11 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/alfresco] appears to have started a thread named [Timer-9] but has failed to stop it. This is very likely to create a memory leak.
mag 22, 2012 2:17:11 PM org.apache.coyote.AbstractProtocol stop
Informazioni: Stopping ProtocolHandler ["http-apr-8080"]
mag 22, 2012 2:17:11 PM org.apache.coyote.AbstractProtocol stop
Informazioni: Stopping ProtocolHandler ["ajp-apr-8009"]
mag 22, 2012 2:17:11 PM org.apache.coyote.AbstractProtocol destroy
Informazioni: Destroying ProtocolHandler ["http-apr-8080"]
mag 22, 2012 2:17:11 PM org.apache.coyote.AbstractProtocol destroy
Informazioni: Destroying ProtocolHandler ["ajp-apr-8009"]
mag 22, 2012 2:17:22 PM org.apache.catalina.startup.Catalina stopServer
Grave: Catalina.stop: 
java.net.ConnectException: Connection refused: connect
   at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method)
   at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
   at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
   at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
   at java.net.Socket.connect(Socket.java:579)
   at java.net.Socket.connect(Socket.java:528)
   at java.net.Socket.<init>(Socket.java:425)
   at java.net.Socket.<init>(Socket.java:208)
   at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:490)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:601)
   at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:371)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:452)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Grazie a tutti in anticipo

[agz]

Prova a leggere qua:
http://wiki.alfresco.com/wiki/Shutdown_Implementation#Shutdown_Backstop.
A me è bastato impostare questo parametro per evitare che alfresco rimanesse appeso in attesa di un kill automatico (dopo 4-5 minuti).