Skip to main content

Seeing this repeating in the ifsalert log ...

Unable to close statement ifs.fnd.sf.j2ee.container.weblogic.FndOracleStatementForWebLogic … timeout.  

Users are also reporting the environment is very slow.  Any ideas?

 

Will restart the middleware after hours at a minimum ...

 

Hi,

 

How was it fixed? I got same issue but IFS support can’t find the root cause.


Hi Suvit … There were a couple of issues with that Apps10 environment last year and the biggest if I remember correctly was network performance between the app server and db server.  Like with most network issues I run into, we never found the root cause.

I’ll check my notes and see if I can find anything more specific.

I’ve been deep in IFS Cloud implementation challenges since February … when you jump to cloud you’ll see a whole new set of issues … especially if you go on-prem.

 


Hi Puzinoj,

 

Thank you for quick response. 

 

There may be a network performance issue between the application server and the database server, but I’ve noticed slowness in only a few IFS screens—not across all functionalities.

 


Have you checked whether your servers have antivirus software installed? This can sometimes slow down application performance. Also, verify that the database instance memory settings are properly configured and review the active sessions in Oracle to see if many are left idle or inactive. In addition check that the midtier connection pool settings are configured correctly and ensure that paging and best performance options are enabled on the servers.


Reply