Michael,

Any chance your java app is opening connections but not closing them? 
It's just guess, but I've made this mistake before.

jerry

Michael Weber wrote:
> We have the following problem here:
> 
> When accessing an owserver (connected via a ds2480 rs232 device), we
> have at first very good performance. We read/write values mainly
> through a java client program (which we now changed to more closely
> follow the way owshell behaves).
> 
> Then, after some time, the java program reports errors, while with
> owdir/owread,owwrite everything still works.
> 
> Then, after more time, owshell programs fail also, and it looks like
> they are unable to open the port.
> 
> At times even the owserver process diappears.
> 
> I now suspect the java clieant to be the problem, and, more
> specifically, the way java deals with ports. We now included a wait
> (1000ms) before the socket is closed  and it seems to be better.
> 
> Anybody had a similar experience and maybe a solution? Last time I had
> owserver crashing a lot I downgraded from 2.5 (or2.6?0 to 2.4. and
> that solved my problem. This time I would like to try to understand
> what is happening. During daytime we can experiment a bit on the
> system (nighttime it is supposed to do Astrophysical observations),
> and the problem is that the calibration lamps are turned on/off by
> owfs. We used to have about 10-20% failures on those switches, now it
> approaches 100%.
> 
> Michael
> 

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to