OAF GATEWAY TIMEOUT ERROR

[Syed Tanweer Ali]

Hi Erman,

Hope you are doing good,Need your suggestion on below issue.

Environment R12.2.5

Module Effected: Payables

User are facing the issue while submitting the electricity bill and are unable to process with the next bills as they are facing timeout issue.

Backend:

While calling concurrent program through OAF Page, Request is getting submitted and completed successfully and we are getting error message "504 Gateway time out error" instead of successful confirmation page. And we see one more time the same concurrent request is getting submitted.

Issue is on multi node setup and not occuring in single node

Thanks and Regards,
Satish

[ErmanArslansOracleBlog]

Which concurrent program is that?
Which OAF page is that?
Are these OAF and concurrent program custom?

[Anusha]

I am Also facing the same issue,could you please help me to resolve the issue.

We are calling concurrent program from custom page

[satish]

Hi Erman,

Thank you!

The program is "Payables Open Interface Import "
It is custom OAF mbook page,they are entering some data and interfacing that data by calling concurrent program

we are having this error only in multi node and not in single node.At beginning we thought this might be a load balancer issue but not sure and need your expertise here

Thanks,
Satish.G

[ErmanArslansOracleBlog]

Hi Satish,

1) Disable load balancer for EBS and retry. What is the result?

2) What do the oacore managed server logs say?

[satish]

Hi Erman,

Thanks for the update,we will try that and get back to you

[satish]

Hi erman,

No errors captured in oacore logs,we have bypassed the load balancer and still we receive the same error. In single node instance when we click on oaf page it is taking 5 seconds and moving to further processing,but in mutinode the same page is running for almost 40 seconds and returning gateway timeout error. Can you please suggest what all we can check in this case

Thanks,
Satish

[ErmanArslansOracleBlog]

Maybe your DB query just hangs.. Check the db side, when your page is running for 40 seconds.. Check the queries, check their wait, try to catch the query.
Also enable OAF trace ( tracing OAF pages) and check the output.

[Sri]

Thanks for the update erman.

We have enabled sql trace and reviewed the trace file but we could nt   see any sql related to OAF page,we will try enabling trace at page level and update you back

[satish]

As this is custom code,no proper information is getting traced.we need your help on steps to bypass the load balancer

below is the plan support engineer updated

       
In order to bypass the load balancer set the s_webenrty_url in your autoconfig file to the actual URL the load balancer directs to

Normally when you are load balancing the s_webenrty_url will point to the loadbalancer url

So when you want to bypass it then it has to be something other than the loadbalancer url

But we dont like to do that and we have followed the below steps

At user level,we have set the below profiles

Apps Servlet Agent : http://<actual host name and domain:webport>/oa_servlets
Applications Web Agent : http://<actual host name and domain:webport>/pls/VIS
ICX: Forms Launcher : http://<actual host name and domain:webport>/forms/frmservlet?form_params=+config=<name of dbc>.dbc
Application Framework Agent : http://actual host name and domain:webport>/
Applications JSP Agent : http://<actual host name and domain:webport>/  

and then we tried to access the url,it is redirecting to http://<actual host name and domain:webport> and then erroring out

Please suggest

[ErmanArslansOracleBlog]

Do the exact opposite of the context file updates that are written in "Using Load-Balancers with Oracle E-Business Suite Release 12.2 Section 2.1: Using Hardware Load Balancers with Single Web Entry Point".

Then run the AutoConfig utility on all the application tier Servers
Restart application server processes
Test your issue and see if it is solved.
If fixed, the scope of the problem will be narrowed down. So you can go deep in the load balancer/custom code configuration.