Consider the following scenario:

   Client sends accounting request, radius processes it (inserts record
into database),
then ACKs it. This ACK is lost in time and space. Client times out, and
sends its accounting
request again. Radius tries to insert it into database -- and fails
miserably because of
uniqueness constraints, since this record has already been stored. Client
now either
gets a NAK or a timeout, and retries again...

  I have seen clients trying as much as five times to get rid of their
accounting record...

  Is there a possibility of saying "when this SQL-error occurs, treat it as

thanx for help, Christian Brem

debis Systemhaus EDVg
Internet Services

Hofmühlgasse 3 - 5, 1060 Wien
Tel.: +43 1 599 07 / 1749
Fax: +43 1 599 07 / 1199
WWW: http://www.debis.at

To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to