cancel
Showing results for 
Search instead for 
Did you mean: 

Authentication causes threads to lock up (JVM issue?)

maximus007
Champ in-the-making
Champ in-the-making
This may or may not be related to why I am having so many authentication problems, but I believe it needs its own thread…

My setup as follows:
-Windows Server 2008 R2
-Alfresco Communty 3.2r2
-JDK 6u18 (x64)
-Tomcat 6.0.24 (x64) w/ ARP dlls
-JVM Confguration:
-Dcatalina.base=D:\Alfresco\tomcat -Dcatalina.home=D:\Alfresco\tomcat -Djava.endorsed.dirs=D:\Alfresco\tomcat\endorsed -Djava.io.tmpdir=D:\Alfresco\tomcat\temp -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=D:\Alfresco\tomcat\conf\logging.properties -Dalfresco.home=D:\Alfresco -Dcom.sun.management.jmxremote=true -XX:PermSize=128m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=64m -Xcomp -Xbatch -Xms2048m -Xmx3072m -Xss1024k 

Any attempt at authentication causes a locks up the java process. Having checked JConsole with the Topthread plugin I have narrowed it down to the SESS_W0_LSN1 (where the 0 & 1 can vary) series of threads. If I try to authenticate again, another thread is created and it locks up (uses 100% CPU). It seems to happen whether I am connecting via CIFS or Webdav, or Alfresco Explorer.

I have had this same issue with inbuilt NTLM and Passthru authentication. It happens whether I'm on a machine which I don't have authentication issues (i.e. XP, Server 2003) or otherwise (Vista, 7, Server 2008)

An example of the thread info from JConsole is as follows:
Name: Sess_W0_LSN1
State: RUNNABLE
Total blocked: 389  Total waited: 0

Stack trace:
org.alfresco.jlan.netbios.win32.Win32NetBIOS.Receive(Native Method)
org.alfresco.jlan.smb.server.win32.Win32NetBIOSPacketHandler.readPacket(Win32NetBIOSPacketHandler.java:133)
org.alfresco.jlan.smb.server.SMBSrvSession.run(SMBSrvSession.java:1264)
java.lang.Thread.run(Thread.java:619)

When  shut down the server I get these sorts of errors (among others):

SEVERE: A web application created a ThreadLocal with key of type [org.alfresco.repo.security.authentication.AuthenticationUtil.ThreadLocalStack] (value [org.alfresco.repo.security.authentication.AuthenticationUtil$ThreadLocalStack@1cad68c5]) and a value of type [java.util.Stack] (value [[]]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.

SEVERE: A web application created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@2d84562d]) and a value of type [org.alfresco.filesys.alfresco.AlfrescoClientInfo] (value [[username:[B@4b35bbb3,MACHINE,Windows 2002 Service Pack 3 2600]]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.

What should I do? Is this an Alfresco or JVM bug?
1 REPLY 1

maximus007
Champ in-the-making
Champ in-the-making
Small update - disabling CIFS appears to stop the issue, even though the hang occurred from authentication in other places.

Disabling CIFS is hardly a good fix!

Should I submit this as a bug?