Alfresco Startup Problem

[syklui]

I have newly installed Alfresco community 2.1 package bundled with Tomcat on standalone PC Windows Vista and the startup had following error messages:

05:50:04,629 ERROR [org.alfresco.smb.protocol.mailslot] Host announce error, 10055endSocketDatagram - No buffer space available, (LANA 😎
05:50:09,630 ERROR [org.alfresco.smb.protocol.mailslot] Host announce error, 10055endSocketDatagram - No buffer space available, (LANA 😎
05:50:19,632 ERROR [org.alfresco.smb.protocol.mailslot] Host announce error, 10055endSocketDatagram - No buffer space available, (LANA 😎
05:50:19,637 ERROR [org.alfresco.smb.protocol.mailslot] Marked LANA as unavailable due to send errors, (LANA 😎
05:50:39,647 ERROR [org.alfresco.smb.protocol.mailslot] Host announce error, 10055endSocketDatagram - No buffer space available, (LANA 😎
05:51:19,647 ERROR [org.alfresco.smb.protocol.mailslot] Host announce error, 10055endSocketDatagram - No buffer space available, (LANA 😎


Appreciate any advice.

[sdavis]

See http://issues.alfresco.com/browse/AR-1379

[syklui]

read through the posts - no clue yet.

Is it the fix in 2.2.0E ?

[vycitalr]

I am also interested in this, and the issue did not give any clear answer. However, I am experiencing a little bit different but very related error, that is:

10:39:17,394 ERROR [alfresco.smb.protocol] Closing session due to exception
org.alfresco.filesys.netbios.win32.WinsockNetBIOSException: 10055:ReceiveSocket - No buffer space available
at org.alfresco.filesys.netbios.win32.Win32NetBIOS.ReceiveSocket(Native Method)
at org.alfresco.filesys.netbios.win32.NetBIOSSocket.read(NetBIOSSocket.java:286)
at org.alfresco.filesys.smb.server.win32.WinsockNetBIOSPacketHandler.readPacket(WinsockNetBIOSPacketHandler.java:111)
at org.alfresco.filesys.smb.server.SMBSrvSession.run(SMBSrvSession.java:1309)
at java.lang.Thread.run(Thread.java:595)
‍‍‍‍‍‍‍‍‍

This happens when accessing CIFS, not when starting server. I use MS Win Server 2003 Enterprise Edition. This problem is really annoying, as it depends on how much the system is loaded in terms of memory. It works for some time, then when some other app eats some more memory this starts to appear. And yet there is a a lot of free memory in system for other apps, but it's like windows cannot use it for sockets allocation. Does anyone know about some windows setting regarding this?

Regards Robert