Visual Builder

Get Involved. Join the Conversation.

Topic

    Nisheeth Ranjan
    Error 504 (Gateway Time-out) while calling...Answered
    Topic posted May 19, 2019 by Nisheeth RanjanSilver Medal: 2,000+ Points, tagged REST, Services, UI 
    130 Views, 13 Comments
    Title:
    Error 504 (Gateway Time-out) while calling Integration from VBCS Application
    Summary:
    Error 504 (Gateway Time-out) while calling Integration from VBCS Application
    Content:

    Hi Experts,

    We are facing “Error 504 (Gateway Time-out)” while calling one of the Integrations from VBCS Application in our PROD instance. When we test this integration from the console and postman it's invoking correctly and performing the task, however, when it's being invoked from the application on a click of a button it gives the Error 504 Gateway Time-out. Please find the attached console log for your reference.

    We had never faced this issue in DEV and UAT and the code is exactly the same in all the environments. Would you be able to advise urgently?

    Best Comment

    David Konecny

    Postman calls are excluded from CORS checks. So successful Postman REST call can still fail in VBCS if your integration REST endpoint is not configured to allow calls from PROD VBCS domain. That would be first thing to check. Though CORS issue should be obvious from log files.

    -David

     

    Comment

     

    • Shay Shmeltzer

      Your attachment is missing.

      You should probably check the log on the server side to see what is causing this.

      • Nisheeth Ranjan

        Hi Shay,

        I see following error in the logs

        <May 20, 2019, 12:31:36,727 AM UTC> <Notice> <Diagnostics> <BEA-320068> <Watch "StuckThread" in module "Module-FMWDFW" with severity "Notice" on server "oiciad2I_server_1" has triggered at May 20, 2019 12:31:36 AM UTC. Notification details: 
        WatchRuleType: Log 
        WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-000337') OR (MSGID = 'BEA-000337')) 
        WatchData: MESSAGE = [STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "608" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@4ae59c82[POST /ic/builder/rt/Order_Request_Form/live/services/auth/proxy/ics10/uri/https/gblprd-lendleasecloud.integration.ocp.oraclecloud.com/ic/api/integration/v1/flows/rest/LL_INSER_HEADE_TABLE_DETAI_SYNCH/1.0/Header]
        ", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace

    • David Konecny

      Postman calls are excluded from CORS checks. So successful Postman REST call can still fail in VBCS if your integration REST endpoint is not configured to allow calls from PROD VBCS domain. That would be first thing to check. Though CORS issue should be obvious from log files.

      -David

       

      • Nisheeth Ranjan

        Hi David, Where do we check for the CORS issue. In the log we have noticed the following error :

        <May 20, 2019, 12:31:36,727 AM UTC> <Notice> <Diagnostics> <BEA-320068> <Watch "StuckThread" in module "Module-FMWDFW" with severity "Notice" on server "oiciad2I_server_1" has triggered at May 20, 2019 12:31:36 AM UTC. Notification details: 
        WatchRuleType: Log 
        WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-000337') OR (MSGID = 'BEA-000337')) 
        WatchData: MESSAGE = [STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "608" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@4ae59c82[POST /ic/builder/rt/Order_Request_Form/live/services/auth/proxy/ics10/uri/https/gblprd-lendleasecloud.integration.ocp.oraclecloud.com/ic/api/integration/v1/flows/rest/LL_INSER_HEADE_TABLE_DETAI_SYNCH/1.0/Header]
        ", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:

        • Shay Shmeltzer

          This doesn't look like a CORS issue. 

          It looks like an issue on your server where the REST service you are trying to invoke can't complete because of a stuck thread.

          Does this service works if you call it from outside VB in the same environment?

          • Nisheeth Ranjan

            Yes, when we invoke this the same integration manually or through the Postman, It works fine.

          • Nisheeth Ranjan

            and the same integration has been working in two of our other environments, it's not working in PROD which is in Ashburn datacenter.

            • Shay Shmeltzer

              I think you'll need to open an SR with Oracle Cloud Support so they can look at the log of your server to see why there is a stuck thread there.

               

              • Nisheeth Ranjan

                We have raised an SR already Shay and awaiting the response from the development team. Thank you for your responses.

                • John Graves

                  Just as an update. I believe this is now working, but no real reason why it wasn't working before.  They are now facing a new issue with running a PCS instance where they are getting an authorisation error.

                  Nisheeth.  Is that true?

        • David Konecny

          In the browser where you run the VBCS app. Open your browser's developer tools and check console for logs and network monitor for individual REST calls and whether there is any other info.

    • Nisheeth Ranjan

      Just to update all that the issue was resolved automatically without making any changes in the environment or the code. We have requested the support team to provide an RCA for the issue.