[jcifs] Deadlock in SmbTree.treeConnect()

[Ingo Rockel]

Hi,

I just had a deadlock on a customers system:

"AJPRequestHandler-ApplicationServerThread-1607":
    waiting to lock monitor 0x0840f7dc (object 0x88700298, a 
java.lang.Object),
    which is held by "AJPRequestHandler-ApplicationServerThread-1509"
   "AJPRequestHandler-ApplicationServerThread-1509":
    waiting to lock monitor 0x0840ef1c (object 0x84db8e18, a 
jcifs.smb.SmbTransport),
    which is held by "AJPRequestHandler-ApplicationServerThread-1607"


   Java stack information for the threads listed above

"AJPRequestHandler-ApplicationServerThread-1607":
	at jcifs.smb.SmbTree.treeConnect(SmbTree.java:121)
	- waiting to lock <0x88700298> (a java.lang.Object)
	at jcifs.smb.SmbTree.send(SmbTree.java:57)
	at jcifs.smb.SmbTree.treeDisconnect(SmbTree.java:161)
	- locked <0x84db8e18> (a jcifs.smb.SmbTransport)
	at jcifs.smb.SmbSession.logoff(SmbSession.java:293)
	- locked <0x84db8e18> (a jcifs.smb.SmbTransport)
	at jcifs.smb.SmbTransport.getSmbSession(SmbTransport.java:138)
	- locked <0x84db8e18> (a jcifs.smb.SmbTransport)
	at jcifs.smb.SmbSession.logon(SmbSession.java:159)
	at jcifs.smb.SmbSession.logon(SmbSession.java:154)
         ...

"AJPRequestHandler-ApplicationServerThread-1509":
	at jcifs.smb.SmbTree.treeConnect(SmbTree.java:123)
	- waiting to lock <0x84db8e18> (a jcifs.smb.SmbTransport)
	- locked <0x88700298> (a java.lang.Object)
	at jcifs.smb.SmbSession.logon(SmbSession.java:161)
	at jcifs.smb.SmbSession.logon(SmbSession.java:154)
         ...

is this an known bug? Or did anyone saw anything similar? The 
jcifs-Version is 1.2.13.


kind regards,

	Ingo