You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@subversion.apache.org by "Ivan Zhakov (JIRA)" <ji...@apache.org> on 2016/08/29 17:30:21 UTC

[jira] [Resolved] (SVN-2935) mod_dav_svn + Apache/mpm_worker don't play nice

     [ https://issues.apache.org/jira/browse/SVN-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Zhakov resolved SVN-2935.
------------------------------
    Resolution: Won't Fix

Resolving as Won't fix: Berkeley DB-based repository back-end has been deprecated.

> mod_dav_svn + Apache/mpm_worker don't play nice
> -----------------------------------------------
>
>                 Key: SVN-2935
>                 URL: https://issues.apache.org/jira/browse/SVN-2935
>             Project: Subversion
>          Issue Type: Bug
>          Components: mod_dav_svn
>    Affects Versions: 1.4.x
>         Environment: Linux
>            Reporter: Subversion Importer
>            Priority: Blocker
>             Fix For: unscheduled
>
>         Attachments: 1_svn-fix.patch
>
>
> I have seen reports of this in email, and experienced it myself, but I cannot find any bug report for this in the bug tracking system.
> The issue is that with mpm_worker, mod_dav_svn will cause the apache process it is in to core dump.  This only happens when the frequency of SVN requests increases (ie. occasional usage does not cause this - however when doing something like a repository diff scan (ie. repeated requests to get all diffs to build a diff database for something like a subversion front-end like FishEye) will trigger it every time).
> It has been previously reported here:
> http://svn.haxx.se/users/archive-2006-02/1317.shtml
> And is also listed as a bug on the apache issue tracker (though it is more likely a mod_dav_svn bug than an apache bug):
> http://issues.apache.org/bugzilla/show_bug.cgi?id=42262
> The latter link includes a stack trace (Thread 9 is interesting), but unfortunately I did not have subversion compiled with symbols at the time, I will re-run it and attach it here.
> Original issue reported by *prez*



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)