General Ledger & Intercompany

Get Involved. Join the Conversation.

Topic

    Alan Rowland
    504 Gateway Error - Journal Upload
    Topic posted December 3, 2018 by Alan RowlandBronze Trophy: 5,000+ Points, last edited February 6, 2019, tagged Financials, General Ledger, Payables 
    233 Views, 5 Comments
    Title:
    504 Gateway Error - Journal Upload
    Content:

    Many of my finance users experience a 504 Gateway timeout error when uploading JE's.  (We also experience the issue with invoices).  We've checked the settings, work with the latest version, uninstall/reinstall, run the health check, etc.   It's intermittent but tends to plague some users more than others.  Size is not necessarily a problem.  It could be a JE for a handful of lines.   I've seen this issue before but don't recall the solution.

    Version:
    R13 18C
    Image:

    Comment

     

    • Felix Beaudoin

      Hey Alan!
      I think this is an issue with the Financials Server. Typically, timeouts like this occur in DBCS and Integration components which the solution is to bounce the server by requesting Oracle to do so.
      504 Gateway Time-out Error (Doc ID 2415728.1)
      Maybe someone else has a different solution but I would raise an SR and ask Oracle if the server needs to be bounced.
      Hope this helps!
      Regards,
      Felix

      • Alan Rowland

        Support asked us to run 'Optimize Journal Import Performance' program.  No issues this month.

        • Felix Beaudoin

          Oh! Your timeout is mostly related to the size of your uploads and not the time before loading the file itself? I thought you were talking about being within Oracle Cloud.

          • Alan Rowland

            We actually had JE's and invoices with less than 100 records time out.  We've gotten the 504 Gateway error in Fixed Assets (a bug that has yet to be fixed), viewing the PO PDF, and maybe one or two other circumstances.

            • Felix Beaudoin

              Ok, that clarifies my understanding. I really thought it was about user timeout issues related to inactivity and not actual transactional procedures. So you're saying that the process to "Optimize Journal Import Performance" resolved the issue for GL Uploads?
              Seems strange that a process would need to be run by the users instead of Oracle just running optimization in the back-end automatically.