[rt-users] Apache2 session problems with rt 3.0.4...

[Guillaume Perréal]

Robert Nickel a écrit :

>On 2003.07.30 20:00:20 +0000, Sebastian Flothow wrote:
>  
>
>>Am Mittwoch, den 30. Juli 2003, um 19:41, schrieb Guillaume Perréal:
>>    
>>
>>>I guess it is related to a connection timeout of MySQL. Maybe the 
>>>Apache::Session module doesn't check if its connection is up (and thus 
>>>don't reconnect).
>>>      
>>>
>>Reconnecting should be handled within the MySQL driver.
>>From perldoc DBD::mysql:
>>
>>       o   DBD::mysql has a "reconnect" feature that handles the
>>           so-called MySQL "morning bug": If the server has dis-
>>           connected, most probably due to a timeout, then by
>>           default the driver will reconnect and attempt to exe-
>>           cute the same SQL statement again. However, this
>>           behaviour is disabled when AutoCommit is off: Other-
>>           wise the transaction state would be completely unpre-
>>           dictable after a reconnect.
>>
>>    
>>
>
>Ok, so is AutoCommit off in the RT code?  Or is this in the Apache module?
>Lastly, can anyone think of a workaround?  I'm not opposed to scripting the
>restart of the web server every day (as this is an 8-5 box) and getting away
>from the problem that way, but I'm wondering if others will be having this
>issue on servers that are 24x7.
>
>Thanks,
>  --Robert
>  
>
It seems this problem is really related to FastCGI as it doesn't happen 
with mod_perl. I guess the Apache::Session module name doesn't start 
with Apache:: for nothing. I didn't tested this with SpeedyCGI -- by the 
way, can someone send a working speedycgi setup on RedHat 8 or 9 ?

But well, as Red Hat's mod_perl truncates POST uploads (even on 8.0, 
just checked it)... choose what you prefer : no attachment or errors ?

-- 
Guillaume Perréal.

Responsable informatique,
Cemagref, groupement de Lyon,
France.

Tél: (+33) 4.72.20.87.87.
Fax: (+33) 4.78.47.78.75.
Site: http://www.lyon.cemagref.fr/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20030731/36c1d52d/attachment.htm>