Re: write(): java.net.SocketException

wugeoffrey <[email protected]> Tue, 6 Nov 2012 05:25:29 +0800
Newsgroups gmane.network.spread.user
Message-ID <[email protected]>
Hi Shawn,I am not a spread developer but an user.
Sounds like something wrong with socket in bad condition like writing data while connection is lost. I think spread is not  supposed for typical bad network conditions like mobile wireless and TCP reliable connection makes thing even worse. It does not handle the exception in a good manner. Centos 5.5 has an old Linux Kernel with probably old network modules I guess.I would try something:1, Try to launch spread in a latest Ubuntu distribution and see if the issue is still there.2, Try to upgrade Java.3, Try C++ API, check if it behaves the same and it would give you more information. 4, Try to handle write and read in a bad conditions in your own way. 
BRPeng Wu

Date: Mon, 5 Nov 2012 12:03:45 -0800
From: 
To: [email protected]
Subject: [Spread-users] write(): java.net.SocketException


Hello,
We are currently using spread and have found this error occurring quite frequently. Unfortunately there is little information on write() errors to be found on the net (many more read() errors).

spread.SpreadException: write(): java.net.SocketException: Connection reset

Would someone be able to describe what would be a potential issue causing this?  I am looking for some guidance as to the source of the error (maybe from a developer) to assist in debugging the error.

We have tried to write several test apps to replicate the bug but have been unsuccessful.  Our system is quite large with many moving parts and it is unclear as to what sequence of events are causing the errors.

We are using spread 4.1 on 64 bit centos 5.5.

Thanks in advance,##Shawn

--


*
  Director Software | Mojix Inc.

  phone : +1.562.221.3474

  email : [email protected]

  web : www.mojix.com


Unless expressly identified to the contrary herein, this email and any attachments contain  and constitute confidential and  proprietary   material  and information for the sole use of the intended recipient. If you are not the intended recipient or otherwise received this e-mail in error, please (i) immediately delete this email and any attachments, print outs and copies of the foregoing and (ii) please notify me immediately by responding to this e-mail message. 



_______________________________________________
Spread-users mailing list
[email protected]
http://lists.spread.org/mailman/listinfo/spread-users

_______________________________________________
Spread-users mailing list
[email protected]
http://lists.spread.org/mailman/listinfo/spread-users