Mercurail Push: Request Entity Too Large

915 views
Skip to first unread message

Andre Himmighofen

unread,
Oct 5, 2012, 7:28:39 AM10/5/12
to scmma...@googlegroups.com
Hello everyone,
I am using scm-manager for some rather big mercurial repositories (~2GB). If I push one of these repositories form my hdd to a hg repository provided by scm-manager the process aborts with:
HTTP Error: 413 (Request Entity Too Large)

I have read several posts from people similar problems with jetty and added
        <Set name="requestHeaderSize">52428800</Set>
        <Set name="requestBufferSize">52428800</Set>
        <Set name="responseBufferSize">52428800</Set>
to the server-config.xml. There was no visible change in behavior, the error still occurs.
The system is a debian 6 vm with 4GB RAM.

I am grateful for every hint.

André

Sebastian Sdorra

unread,
Oct 5, 2012, 7:46:25 AM10/5/12
to scmma...@googlegroups.com
Hi,
Is there an exception in the log file? Could you try to split the push
(with hg push -r xxx)?

Sebastian

2012/10/5 Andre Himmighofen <andre.hi...@googlemail.com>:

Andre Himmighofen

unread,
Oct 5, 2012, 9:33:10 AM10/5/12
to scmma...@googlegroups.com
Hi,
the log contains nothing about the aborted push.
I have tried to push only some revisions but "the big one" where many files were added is still failing.

André

Sebastian Sdorra

unread,
Oct 6, 2012, 10:15:10 AM10/6/12
to scmma...@googlegroups.com
Hi,
Do you have many small files or do you have big files in your commit?
Do you use the largefile extension of mercurial? Could you enable
trace logging for all components and post the output?

Enable trace logging for all components:
- change the following lines in the logging.xml, from

<logger name="sonia.scm" level="INFO" />

- to

<logger name="sonia.scm" level="TRACE" />

- and from

<root level="WARN">

- to

<root level="TRACE">

Andre Himmighofen

unread,
Nov 26, 2012, 4:07:01 AM11/26/12
to scmma...@googlegroups.com
Sorry for the large delay.
I made an upgrade to 1.22 last week and the error vanished. What ever you have done between 1.20 and 1.22 fixed it.

André
Reply all
Reply to author
Forward
0 new messages