topic Re: No more connections can be made... in Alfresco Archive

No more connections can be made...

pat — Thu, 26 Oct 2006 13:17:39 GMT

Hi,We are running Alfresco 1.4 RC1 on a Red Hat AS 3 server and connecting viaCIFS from WinXP workstations. We get regulary the following error messagein Window XP (usually after processing a lot of files):"No more connections can be made to this remote computer because there arealready as many conn

Re: No more connections can be made...

killinchi — Mon, 13 Nov 2006 18:36:19 GMT

I am having this same issue running on Windows Server 2003. Any luck on finding a resolution?

Thanks

Re: No more connections can be made...

callermd — Wed, 20 Dec 2006 02:20:45 GMT

WinXP Pro connection to Fedora Core 5. Alfresco 1.4.

Sometimes doing net use /delete works, but other times not. Bouncing tomcat solves it temporarly.

Re: No more connections can be made...

callermd — Mon, 02 Apr 2007 23:37:25 GMT

This is killing us..

We upgraded to 2.0 and Fedora Core 6 with no luck…

Re: No more connections can be made...

gary_spencer — Thu, 05 Apr 2007 08:59:42 GMT

Hi,

If you could email me a packet trace of this problem I can compare with a similar problem that was fixed recently. The fix is currently in the 1.4.x code as I'm waiting on feedback to see if it's actually fixed, then I can merge it up to the 2.x code.

Cheers

Gary

Re: No more connections can be made...

kingedgar — Tue, 10 Apr 2007 19:53:59 GMT

We are having the exact same issue with Centos4.4 and Alfresco2.0.

What kind of packet trace do you want? TCPDUMP? Anything specific? I am willing to do whatever it takes to help fix this as it is killing our DTD operations.

Thanks for help in advance !!!

Re: No more connections can be made...

gary_spencer — Tue, 10 Apr 2007 19:57:36 GMT

Hi,

Tcpdump is ok as long as you make sure you get the whole packets, I think the command line option is '-s 0'.

Cheers

Gary

Re: No more connections can be made...

kingedgar — Tue, 10 Apr 2007 21:09:47 GMT

PM and Email sent with packet capture.

Re: No more connections can be made...

tyve — Wed, 02 May 2007 09:06:49 GMT

It this resolved or reported as an issue? We can reproduce the problem in Alfresco 2.0 running on Solaris 10 by uploading 500 small html files. I use xcopy over a cifs mounted drive and i locks Alfresco every time with "No more connections…".

Re: No more connections can be made...

gary_spencer — Wed, 02 May 2007 09:14:46 GMT

Hi,

There have been some recent fixes for this problem, but there may be more than one problem. If you could send me a tcpdump packet trace that would be useful to see if it is the same problem or not.

Cheers

Gary

Re: No more connections can be made...

plachance — Sat, 19 Jan 2008 09:47:05 GMT

Hi,

Any news on this issue?

I am aving this problem with a Unison job running on Windows 2003 R2 accessing a CIFS map exported by Alfresco CE 2.1 running on Windows XP Pro SP2.

It happens every time I synchronize many thousand files (~41000 files, ~9100 folders).

Workaround : unmapping/remapping the drive on client side or restarting Tomcat on server side, but it is quite annoying…

Re: No more connections can be made...

simonbrocklehur — Thu, 31 Jan 2008 14:59:15 GMT

We get this problem too… running Alfresco 1.4 on Windows Server 2003.

I assume it's the following bug…

http://issues.alfresco.com/browse/AR-1343

and so isn't fixed in any version of Afresco?

It's causing us no end of problems for some users who use the CIFS interface a lot.

Any kind of update on where they are with this from the Alfresco team would be really appreciated…

Re: No more connections can be made...

rdanner — Fri, 01 Feb 2008 04:13:19 GMT

We get this problem too… running Alfresco 1.4 on Windows Server 2003.

I assume it's the following bug…

http://issues.alfresco.com/browse/AR-1343

and so isn't fixed in any version of Afresco?

It's causing us no end of problems for some users who use the CIFS interface a lot.

Any kind of update on where they are with this from the Alfresco team would be really appreciated…

We see the same issue with 2.0.1E. It is quite a problem for us however I somehow managed to miss this thread and have long considered it an issue on the remote end. Any information on this or any progress on this issue would be of great service to us and as it seems, many others.