RE: Each access causes need of db_recover?

I'm surprised that not one person has been able to give me even
one hint about where to start debugging this issue. I'm not
familiar with the internals of apache, nor the internals of
subversion, so I'd rather have someone who is point me at places
where breakpoints may make sense; things to check in config/setup;
etc rather than taking it from the top.

If anyone knows why apache 2.0.40 with subversion 3141 would cause
the database to get corrupted when being browsed with Internet
Explorer 5.5, or how to most easily go about debugging such a
problem, I'm again asking for pointers to where to start.

Cheers,

                        / h+

[btw: dev@subversion is now set to plain text mode in Outlook. The
joys of Microsoft software!]

-----Original Message-----
From: Jon Watte [mailto:hplus@mindcontrol.org]
Sent: Saturday, September 07, 2002 2:59 PM
To: dev@subversion.tigris.org
Subject: Each access causes need of db_recover?

Hi all,

I wanted to check with the list before posting a bug. I got
the trunk of svn (and all the required upgraded components)
yesterday (Friday) and built/installed apache 2.0.40 with
svn as of revision 3141. I also built and installed php 4.2.3
with all of its baggage (I needed this because of the Apache
upgrade).

Things seemed to work okay. I created a repo and imported
the neon 0.23.3 sources into a "neon" subdirectory. I can
browse this directory locally.

However, when browsing using Internet Explorer 5.5 hitting
the repository directly, I could initially read a few of the
neon html files, but when I got to chap02.html, I got an XML
format error. After this error, pretty much every access to
the neon subdirectory will tell me I need to run db_recover.

Running db_recover will allow me to hit one file, which will
typically give an XML error on the <hr noshade> line as
emitted by the Subversion server browse code, and then I need
to run db_recover again.

I searched the mailing list and the bug db, but couldn't find
any issues similar to this.
I also tried turning off keepalive in httpd.conf, but that
seemed to make the problem, if anything, worse.

The only inkling I've gathered so far is that perhaps svn is
sending data which IE interprets as text/xml, and tries to
apply some xslt on, whereas the text is actually text/html (it
looks very much like HTML to me). Perhaps this parse error
will cause IE to terminate the connection in such a way that
SVN gets a premature shutdown.

Any insights? Ideas for debugging, pointers to FAQs I missed,
patches to apply and marshmallows are all welcome. I'm not
(very) afraid of GDB.

Cheers,

                / h+

--
  "Oh, here we go. 'Poor me, my father never gave me 
   what I wanted for my birthday, boo hoo, my daddy's 
   the Dark Lord of the Sith.. waahhh wahhh!'" 
                                   -- Aussie Beer Ninja
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org