Re: [Jamod-devel] Does Jamod cause "Too many open files." error ?

[Jim R. <jr...@er...>]

Glenn,

I think, when I was looking at the code that there is no timeout for an 
open slave socket.  That is, if the client loses contact with the server 
and the server doesn't realize it, I think that the server will never 
close the socket.

The classic case of this is, start communication, pull the network while 
no request is in progress, stop the client, reconnect the cable.  The 
server will never know that the connection was lost.

Jim

Glenn Davidson wrote:
> Hello,
> 
> I am using jamod 1.0 (fix2) and my application eventually runs out of file
> handles. I am investigating the source of this problem and woud like to
> know if there has ever been a bug reported for Jamod that could result
> in too many files being open.
> 
> I am specifically looking at the ModbusTCPTransaction class's
> "execute" method. In the case of a inet address for a host that does
> not exist is it possible that his method is opening a TCP socket and
> then throwing the "ModbusIOException: Connecting failed." without
> closing the TCP socket (file handle) ?
> 
> I can do a work around in my application by catch the exception
> and then calling the close method for the TCPMasterConnection
> but I wanted to get some feed-back on this theory first.
> 
> Thanks.
> 
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Jamod-devel mailing list
> Jam...@li...
> https://lists.sourceforge.net/lists/listinfo/jamod-devel

-- 
Jim Redman
(505) 662 5156 x85
http://www.ergotech.com