Re: Failed to contact xxxx-1085, ellpack

On Oct 4, 2005, at 1:30 AM, John Pollard wrote:

> Thank you Sacha, it took me a while to grasp what you were saying  
> about ellpack. Should I use a different range of ports?

That's the range that I use, so no.  The only reason to not use a  
port is if it's already in use.  :-)


> If so, what range is sensible and can I add them to /etc/services  
> along with my own process names.
>
Ports 2000+ are usually pretty safe.  Don't worry about it unless  
you're seeing problems with applications binding to specific ports.   
As for adding them to /etc/services, there's no reason not to other  
than the fact that it really gets you nothing: it's just a port # to  
service name mapping file -- if you want to refer to that port by  
name, then go for it, otherwise just use the number and don't screw  
with the file.


> When we were running on Panther Server, we had this type of problem  
> prior to WO5.2.3 which seemed to fix it. But since we have moved to  
> Tiger (Client), JavaMonitor has seemed temperamental and these  
> CLOSE_WAIT problems are cropping up again. Does anyone know if  
> Apple have this back on their bug list again? I am not convinced  
> that any of my app instances are going south, other than being cut  
> off by wotaskd.
>
That is possible.  The problem is definitely less severe that it was  
in 5.2.3, FWIW...


sacha


--
Sacha Michel Mallais             Senior Developer / President
Global Village Consulting Inc.   http://www.global-village.net/
PGP Key ID: 7D757B65             AIM: smallais
Bottom posting is your friend:
http://www.river.com/users/share/etiquette/

_______________________________________________
WebObjects-admin mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-admin