3 Replies Latest reply on Jul 13, 2016 4:22 AM by velias

    JIRA e.g. https://issues.jboss.org/browse/JBIDE can't be used in China without VPN

    paul.verest

      Google services are absent in mainland China.

       

      JIRA make use of google APIs, that make JIRA page load extremely slow (1 minute)

        • 1. Re: JIRA e.g. https://issues.jboss.org/browse/JBIDE can't be used in China without VPN
          velias

          Hi Paul,

           

          thanks a lot for the report. It is a bit problematic to debug it outside of China :-( Are you please able to find which exact request blocks the page loading (using developer tools in your browser)? Because as I know we perform all google requests in an asynchronous manner, which should not block page loading/rendering if these services are not available.

           

          Thanks a lot in advance

          • 2. Re: JIRA e.g. https://issues.jboss.org/browse/JBIDE can't be used in China without VPN
            paul.verest

            Just did use of Network tool.

             

            959519.png

            There's no failed DNS resolutions or inaccessible servers, but mystical batch.js that needs to load 1MB twice and questionable dependency on success of avatar loading for next processing step.

            • 3. Re: JIRA e.g. https://issues.jboss.org/browse/JBIDE can't be used in China without VPN
              velias

              Thanks Paul.

              So it seems the problem has nothing to do with google services.

              The very long load of avatar image is really strange, we use Akamai Content Delivery Network for static.jboss.org domain to improve load times around the world. I have no idea why this is a problem on your location :-(

              batch.js if some mechanism in jira which allows to join more small js files provided by more componenets into bigger one, it depends on appended params what is exactly returned in it. And yes, it is strange why load of it is blocked until avatar image load.

               

              BTW is this bad behavior repeatable in Chrome (is the problem with same requests when you reload the page), and is it also repeatable in another browser (eg. Firefox).