[Trac] Browsing changesets causes "wedged" reposity

[Stian Grytøyr]

Hello all,

First, kudos to the Trac developers. I have just recently started using
Subversion and I'm finding Trac to be a wonderful companion.

However, I have this very annoying problem where browsing changesets
will eventually wedge my repository. After looking at a few changesets
(maybe 4-8) Trac will hang after outputting most of the changeset, and
when I then try to view another, there is no response at all. At this point
I will have to do "svnadmin recover" to fix the problem.

According to the docs and faqs I've seen, wedges are almost always
caused by wrong permissions and/or processes that access the 
repository without finishing. I'm inclined to believe that this is caused
by the latter, since I believe my permissions are ok (I have created
wrapper scripts for svn and svnadmin that set the correct umask, and
the db dir is g+s).

The Apache error log shows the following:

(70007)The timeout specified has expired: ap_content_length_filter:
apr_bucket_read() failed

I'm running SuSE Linux Pro 9.1, Apache 2.0.49-23, Python 2.3.3,
Subversion 1.0.0-51 and Trac 0.8. I have the default database, so
I'm assuming it's Berkeley DB.

Is there a solution to this problem?

-- 
Best regards,
Stian Grytøyr