in reply to Net::FTP and Ports

I have to agree with some of the others. I don't think this is a problem with Net::FTP. You have experienced a problem with your code and are speculating on what you think is a problem in Net::FTP.

Show the actual code (make a small program that illustrates the problem) you are using to interact with Net::FTP.

Without seeing your code, this is just a guess, but perhaps you aren't closing the FTP connection each time? Either destroy the Net::FTP object and re-create it with each iteration, or make sure you are calling 'login'/'quit' each time.

Replies are listed 'Best First'.
Re: Net::FTP and Ports
by Anonymous Monk on Feb 06, 2004 at 14:10 UTC

    Now this is where it gets interesting... I've already added tracking to see where the ports get opened and closed, and I am definitely constructing and destructing (destroying?) correctly:

    WARNING:
Opened port 1769 for FTP at c:/Perl/site/lib/Net/FTP.pm line 803.
WARNING:
Closed port 1769 for FTP at c:/Perl/site/lib/Net/FTP.pm line 929.

    The code I'm using a little bit lengthy because I'm wrapping Net::FTP within another package to present a consistent interface to another system. Also, it's not the number of iterations that causes the problems as now I've added a counter onto the system to see how many iterations it gets to before crashing out, and it's breaking the 255 barrier easily, indicating that it is most likely closing sockets fine.

    I've come across this before on Linux some time ago, with code that used to run for weeks and then suddenly fail to make a connection.

[reply]

      Dang and Blast it.

      Turns out it's a problem with ActiveState's PerlSvc Freestanding Exe builder which for some reason limits the number of sockets that can be opened (from startup to destruction) to 169!

      Upgrading from V2.1 to V5.3 seems to have fixed the problem

      Thanks to everyone for their help,

      Julian

[reply]

In Section Seekers of Perl Wisdom