[ILUG] Ports on Java / Linux (Slightly OT)

[Thomas B. Quillinan]

On Wed, 04 Oct 2000, Mark Fallon wrote:
> Lorcan Hamill wrote:
> > My guess is that you're not calling Socket.close(), but just letting
> > your socket objects go out of scope.  That's fine if the garbage
> > collector kicks in, because the Socket's finalize() probably calls
> > close(), but the gc just ain't happening.  This is quite common - the gc
> > only kicks in if you're running low on memory - so it's easy to run out
> > of
> > non-memory resources if you're not careful to call "cleanup" methods
> > like Socket.close() before letting your objects go out of scope.
> > The GC on Windoze is probably more aggressive than the one you're now
> > dealing with.
> >
> > I could be wrong about all this - I've never seen this happen with
> > sockets, but I *have* seen exactly the same problem with an app
> > that processes ordinary files.
> >
> > Good luck.
> >
> > Lorcan
>
> You can force garbage collection with:
>
> 	System.gc();
>
> You can also force finalize to be called on all objects
> waiting for garbage collection with:
>
> 	System.runFinalization();
>
> Regards,
>
> Mark

Thanks for the ideas...
Im actually using all the sockets I've currently open - so this isn't the 
problem (I think)
However I have an inkling that I have run out of sockets - Is there any way 
of increasing the number that an ordinary user is allowed to open?
thanks
tom.
-- 
regards,

Thomas B. Quillinan
Security Researcher at Centre for Unified Computing (http://www.cuc.ucc.ie)
finger tom at skynet.ie for my PGP Key