Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-38007

504 gateway timeout in sse-gateway/configure https://ci.blueocean.io

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • blueocean-plugin
    • None
    • 1.0-beta-1, 1.0-b05/b-06

      I was trying to play with ci.blueocean.io and nothing was loading. Looking at the chrome developer tools, I see that sse-gateway is causing timeout.

      The complete HTTP archive here

      jamesdumay and I were chatting when I had that issue, and he said it is working for him. Classic Jenkins UI was working fine, too.

      jamesdumay sounded like he knows about this lock inside SSE gateway that had caused a similar problem in the past, so this might be a known problem?

          [JENKINS-38007] 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io

          Michael Neale added a comment - - edited

          FYI sometimes the timeout is a non-issue, just the way chrome shows the http 1.1 connection for SSE (it it stays open for a minute or so, and sometimes shows up as "timing out").

          kktest11 did you see any errors in console other than that? can you attache them?

          Also were you logged in or anon?

          Michael Neale added a comment - - edited FYI sometimes the timeout is a non-issue, just the way chrome shows the http 1.1 connection for SSE (it it stays open for a minute or so, and sometimes shows up as "timing out"). kktest11 did you see any errors in console other than that? can you attache them? Also were you logged in or anon?

          Michael Neale added a comment -

          tfennelly not sure if there is much to diagnose, I am not seeing this, but worth a look (perhaps at least to eliminate this, may not actually be SSE at all).

          Michael Neale added a comment - tfennelly not sure if there is much to diagnose, I am not seeing this, but worth a look (perhaps at least to eliminate this, may not actually be SSE at all).

          Michael Neale added a comment - - edited

          If this is the SSE deadlock, it would show up more like: https://issues.jenkins-ci.org/browse/JENKINS-37921

          Michael Neale added a comment - - edited If this is the SSE deadlock, it would show up more like: https://issues.jenkins-ci.org/browse/JENKINS-37921

          Tom FENNELLY added a comment -

          I'm not sure what one's supposed to look at in that Http archive log, but I see a rest api call timing out too (before SSE config requests).

          I'm going to look at removing the locking completely from the SSE config path and make it async.

          Tom FENNELLY added a comment - I'm not sure what one's supposed to look at in that Http archive log, but I see a rest api call timing out too (before SSE config requests). I'm going to look at removing the locking completely from the SSE config path and make it async.

          Thorsten Scherler added a comment -

          Not sure if related but yesterday I saw not the same issue but similar while updating/fixing AT https://github.com/jenkinsci/blueocean-acceptance-test/pull/34

          I was up to update the sse-gateway plugin to 0.0.8, but that breaks the AT.
          In standalone the test case (ff never starts up) simply hang.
          It hangs around the "sse handshake"

          Thorsten Scherler added a comment - Not sure if related but yesterday I saw not the same issue but similar while updating/fixing AT https://github.com/jenkinsci/blueocean-acceptance-test/pull/34 I was up to update the sse-gateway plugin to 0.0.8, but that breaks the AT. In standalone the test case (ff never starts up) simply hang. It hangs around the "sse handshake"

            tfennelly Tom FENNELLY
            kohsuke Kohsuke Kawaguchi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: