Re: NET_ERROR_ON_SESSION

Most likely, the daemon is closing the connection and your sender thread is seeing a permanent error recorded on the mailbox and is returning a generic error.  The daemon is most likely closing your connection due to you not reading from the mailbox fast enough.  For example, if you have a sending app. that joins a group and then never reads, then its connection will be closed after a ~1000 msgs are not read from the mailbox.  Most likely, a previous call already failed with a CONNECTION_CLOSED error.

If you can describe a bit better which app. is dying (i.e. - sender or receiver) and whether they are joined to any groups that would be helpful.  Also, check your code and make sure you are checking all return codes, as almost surely the NET_ERROR_ON_SESSION is not the first time an error is returned.

Cheers!

-----
John Lane Schultz
Spread Concepts LLC
Phn: 301 830 8100
Cell: 443 838 2200

On Feb 17, 2011, at 12:42 PM, Miguel Araújo wrote:

Hello.

I am using Spread on a group of machines connected through an LAN. One of the machines is sending messages to the others with a not really high rate.
After some minutes I receive the NET_ERROR_ON_SESSION message:

"SP_error: (-18) The network socket experienced an error. This Spread mailbox will no longer work until the connection is disconnected and then reconnected"

Even with small rates of "message sending" the Spread does not handle it too much time and ends with the same error.

So, what is happening here? What are the limits of Spread in this case? Throughput, network, etc.

I would appreciate any help and information, and I am available to provide more information if necessary.


Thanks and kind regards,

--
Miguel Araújo
| [email protected] |




_______________________________________________
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