[Spread-users] spread killed session, why?

M S martin4321234 at googlemail.com
Mon May 25 13:08:46 EDT 2009


We observed the following scenario:

The spread.log reports that a connection to one of the group members
has been killed but we don't understand the reason.

This spread daemon is running at the same host as the affected group
member application process. The application process is running
continuously for many days and is still running without problems. At
the same time several other application processes at the same machine
had problemfree spread connections.

One second after the kill message in spread.log our application
process failed sending a SAFE_MESS message using spread because of an
sperrNo="Illegal session" error. One second later our application
performed a reconnect and the spread communication is working fine.

We do not understand why the spread daemon decided to terminate the
connection to the application process. Could it be caused by an
overload situation?

In which cases will spread terminate a connection?
How does spread monitor the reachability of a registered process
running at the same machine?

Any hint is greatly appreciated.
Kind regards,
Martin
--
spread-Version: 3.17.4 with perl, Platform: Solaris 2.10
spread.log:
2009-05-13 02:20:17 GMT G_handle_kill: #RD02#host327 is killed
2009-05-13 02:20:17 GMT G_handle_kill in GOP
2009-05-13 02:20:17 GMT G_handle_kill: Mask for group E:RD02 set to 0 0 0 11
2009-05-13 02:20:17 GMT G_handle_kill: Mask for group EC set to 0 0 0 ff
2009-05-13 02:20:19 GMT G_handle_join: #RD02#host327 joins group E:RD02
2009-05-13 02:20:19 GMT G_handle_join in GOP
2009-05-13 02:20:19 GMT G_handle_join: Mask for group E:RDM2 set to 0 0 0 11
2009-05-13 02:20:19 GMT G_handle_join: #RD02#host327 joins group EC
2009-05-13 02:20:19 GMT G_handle_join in GOP




More information about the Spread-users mailing list