[Spread-users] Spread daemon fails frequently!

[DaiLin(戴霖)]

I have four spread daemon run on four computer with Windows2000. Some or all of them fails in membership.c at line 1583(in function Fill_form1) with overflow error frequently!
Is this a bug with Spread?

The message in log file is:
	Memb_token_loss: I lost my token, state is 1
	Scast_alive: State is 2
	Memb_handle_message: handling alive message
	Handle_alive in SEG
	Memb_handle_message: handling alive message
	Handle_alive in SEG
	Scast_alive: State is 2
	Memb_handle_message: handling join message from -1408235423, State is 2
	Scast_alive: State is 3
	Memb_handle_message: handling join message from -1408235423, State is 3
	Scast_alive: State is 3
	Memb_handle_message: handling join message from -1408235423, State is 3
	Scast_alive: State is 3
	Memb_handle_message: handling join message from -1408235423, State is 3
	Scast_alive: State is 3
	Memb_handle_message: handling join message from -1408235423, State is 3
	Scast_alive: State is 3
	Memb_handle_token: handling form1 token
	Handle_form1 in REPRESENTED
	Memb_handle_token: handling form1 token
	Handle_form1 in FORM
	Memb_handle_token: handling form2 token
	Handle_form2 in FORM
	Memb_handle_token: handling form2 token
	Handle_form2 in EVS
	Memb_transitional
	G_handle_trans_memb: 
	G_handle_trans_memb in GOP
	Memb_regular
	Membership id is ( -1408235423, 1062917910)
	
	G_handle_reg_memb:  with (172.16.8.97, 1062917910) id
	G_handle_reg_memb in GTRANS
	Sess_read: Message has type field 0x800000a0
	Sess_read: queueing message of type 16 with len 0 to the protocol
	Sess_read: Message has type field 0x800000a0
	Sess_read: queueing message of type 16 with len 0 to the protocol
	Memb_handle_message: handling alive message
	Handle_alive in OP
	Memb_handle_message: handling alive message
	Handle_alive in OP
	Memb_handle_message: handling alive message
	Handle_alive in OP
	Memb_handle_message: handling alive message
	Handle_alive in OP
	Memb_handle_message: handling alive message
	Handle_alive in OP
	Memb_handle_message: handling alive message
	Handle_alive in OP
	Memb_handle_message: handling alive message
	Handle_alive in OP
	Memb_handle_message: handling alive message
	Handle_alive in OP
	Memb_handle_message: handling join message from -1408235427, State is 1
	Handle_join in OP
	Memb_handle_message: handling join message from -1408235427, State is 1
	Handle_join in OP
	Memb_handle_message: handling join message from -1408235427, State is 1
	Handle_join in OP
	Memb_handle_message: handling join message from -1408235427, State is 1
	Handle_join in OP
	Memb_handle_message: handling join message from -1408235427, State is 1
	Handle_join in OP
	Memb_token_loss: I lost my token, state is 1
	Scast_alive: State is 2
	Memb_handle_message: handling alive message
	Handle_alive in SEG
	Memb_handle_message: handling alive message
	Handle_alive in SEG
	Scast_alive: State is 2
	Memb_handle_message: handling join message from -1408235427, State is 2
	Scast_alive: State is 3
	Memb_handle_message: handling join message from -1408235427, State is 3
	Scast_alive: State is 3
	Memb_handle_message: handling join message from -1408235427, State is 3
	Scast_alive: State is 3
	Memb_handle_message: handling join message from -1408235427, State is 3
	Scast_alive: State is 3
	Memb_handle_message: handling join message from -1408235427, State is 3
	Scast_alive: State is 3
	Memb_handle_token: handling form1 token
	Handle_form1 in REPRESENTED
	INSERT HOLE 2 IS 3
	INSERT HOLE 2 IS 4
	INSERT HOLE 2 IS 5
	INSERT HOLE 2 IS 6
	..................