Ebusiness Suite Health Check : AS

R12 Application Server Control

 

 

• Allows you to monitor JVM usage through a web interface
  
  • Number of sessions
    
  • Heap Usage
    
  • Number of active threads
    
  • Thread deadlocks
    
• With version 10.1.3.1 or above, you can monitor any JVMs in each group
  

 

• AOLJ Connection Pool (dbc configuration)
  
• Start with a reasonable default such as 100 or 200.
  
  • FND_JDBC_MAX_CONNECTIONS=200
    
  • Tune setting as per the amount of user concurrency (per JVM).
    
• AOLJ automatically decays idle connections and resizes the pool
  
• Reduce the number of OXTA JDBC connections
  
  • 11i: In jserv.properties file, add the following entries
    

    wrapper.bin.parameters=-DOXTAOutThreads=1
    

    wrapper.bin.parameters=-DOXTAInPoolSize=1
    

  • R12: In oc4j.properties     OXTAInPoolSize=1 OXTAOutThreads=1
    
  • If running multiple JVMs, the OXTA connections can be a
    

  significant portion of the total JDBC connections.
  

  • Automatically set in 11i10
    

 

 

• AOLJ Connection Pool (dbc configuration)
  
  • Disable sanity checks in production environments
    
    • FND_JDBC_USABLE_CHECK=false
      
    • FND_JDBC_PLSQL_RESET=false
      
• AOLJ Connection Pool Monitoring
  
  • Use the JSP (AoljDbcPoolStatus.jsp) to monitor the connection pool
    
    • Lists DBC configuration parameter settings.
      
    • Connection Statistics
      
    • Locked Connections
      
    • Available Connections
      
    • Closed Connections
      
    • Allows drill-downs to determine source of the connection.
      
    • For R12, should also inspect error logs for connection leaks