Mike McCauley wrote: > Its a first for me too. > I could conceive of a 'DisconnectAfterQuery' flag that would disconnect after > every SQL query was finished, but Im reluctant to add it since I dont think > it would be widely useful, and when it was used it would significantly slow > things down.
Performance is not an issue for us right now, since we barely get a few dozen authentications per day. > Do I understand from the below that you are connecting to MS-SQL from Radiator > running on a FreeBSD box? > > We havent heard of similar behaviour, even from FreeBSD to MS-SQL. It is > possible that using keep-alives or similar might alleviate the problem? > > Cheers. The problem is our MS SQL Server 7.0 (yuck!), service pack 2 drops connections if they're idle for a long enough time: Tue Aug 13 09:39:24 2002: ERR: do failed for 'insert into failedattempts (LoggedAt,User_Name,NAS_IP_Address,Caller_ID,NAS_Port,Failure_Message, Active_Handler) values ('2002-08-13 09:39:24.000','soconnell','10.0.2.201','', '29374','''Bad Password''','prodnetilla')': Server message number=10018 severity=9 state=0 line=0 server=OpenClient text=The connection was closed I am just looking for a a quick work-around. MS' site actually has a blurb about configuring time-outs for DB connections, but we couldn't find such an option at least for our service pack. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.