http error 400 bad request

Viewing 2 posts - 1 through 2 (of 2 total)
  • Back to forum
    Posted in: Muster 9
  • Alex Oddbratt
    26th March 2021 at 4:54 pm #34361

    We have a tool that submits multiple jobs to muster, basically one job per shot. Each of these jobs then opens Maya and submits one job per renderlayer. ie a job that submits jobs. This causes several machines to connect to the dispatcher at once while submitting the jobs and we tend to get “http error 400 bad request” errors every so often.
    If we try reiniting the job after a short pause it works fine so there’s not an issue with the submission command or usename aso.

    It feels more like if there’s a max connection problem with the dispatcher, ie if to many jobs are running with open connections some of them will fail to submit.
    Is there a setting somewhere in the dispatcher that controls max connections over http or is this a totally different type of error.

    We are using Muster 9.0.14 build 11518

    Leonardo Bernardini
    28th March 2021 at 2:22 pm #34362

    Hi Alex,

    Yes there’s a maximum number of concurrent connection in the web server as well as maximum number of pending connections and working threads (something like Apache…) you can fine tune them in the Web server preferences of the Dispatcher.
    By the way, 400 is a bad request, while the connection should be gracefully closed, but this depends on the browser/api so maybe your Python or custom script returns you a 400 error in this situation

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.