Weird behaviour when using rabbitmq etc.

[Stefan]

Hi running Rhodecode 1.7.1 with RabbitMQ works good as long as not too many people try to work with it. The ballpark here is like 5 people. E.g., forking a repository takes some time and as I understand is executed using background tasks in rabbitmq, they seem to be scheduled for later execution if there is another or too many other rabbitmq tasks running, right? The problem though is, that this is not reflected in messages produced by RhodeCode, e.g., when forking it immediately returns saying forked repository accessible under the following URL, but it is not there until previous tasks in rabbitmq are processed, which leads the user to believe it was not created and creates a new one over and over. Is there any other way to avoid this?

Regards

Stefan

[Yuriy Romanenko]

the same issue. Even more, getting Error 500 when try to immediate access to the page after fork.

Понеділок, 15 липня 2013 р. 14:47:45 UTC+3 користувач Stefan написав: