Bad Gateway when trying to interact with remote mercurial repository

[Benjamin Probst]

Hi

Currently we have some local mercurial repositories, that are not able to interact with the remote repository.
Each time we try a command like push, pull, incoming or outgoing we receive the abort "HTTP Error 502: Bad Gateway.

On the log, there is no entry that indicate that there was a problem.

If we clone the exact same repository from the remote server, export/import the changes and push again, it work.
The local repositories with the problem can also be pushed against the same remote repository over "hg serve", so it should not be a problem of the local repository.

Our setup is:
Local:

• Mercurial 2.7

Remote:

• Mercurial 2.5.4
• JBoss 4.3
• scm-manager 1.33 with ldap-auth plugin

Has anyone seen this problem before or can give me some advice?

[Sebastian Sdorra]

Hi,

I think the problem comes from a too small http header size. I don't know how to increase the header size for a jboss, but here are examples for tomcat and glassfish:

https://bitbucket.org/sdorra/scm-manager/wiki/applicationserver

Sebastian

2013/9/19 Benjamin Probst <beni....@gmail.com>

--
You received this message because you are subscribed to the Google Groups "scmmanager" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Benjamin Probst]

Hi Sebastian

Thank you for your quick response.

This was exactly our problem, now with a maximum header size of 16384 we can push our changes.

For other jboss (4.3) users, here the config I changed:
In JBOSS_HOME\/server/PROFILE/deploy//jboss-web.deployer/server.xml there is a connector with the protocol "HTTP/1.1", there I changed the attribute maxHttpHeaderSize to 16384 .

Benjamin