Issue for Weblogic-3

JDBC

Stale connections causing high CPU and high memory utilization and eventually breakdown of database.

Soln:

The hardware and software could not be easily replaced due to the cost it.They can be incurred due to complexity of the application. So the challenge was to make the best utilization of the database, reduce the connections, if possible effectively use the connections made and refine the code

All the  connections to the database were being made by the connections pools configured on Web logic, so web logic was the target for refinement. 

During the periods when the issue occurred it was observed that the number of sessions rapidly increases from 1400 to 1800,database was capable of handling 1400 sessions it couldn’t support 1800 sessions at all. Most of these 1800 sessions were connections created by web logic in response to application request. 

We mainly concentrated on two parameters:

1. Shrink Frequency 

2.Inactive Connection Timeout. 

Shrink Frequency: The number of seconds  before Web Logic Server shrinks the connection pool to the original number of connections or number of connections currently in use. 

Startup Issue:

when you are  tying to start Web logic as a Windows service the Service Manager throws an exception – 
“Error 1067 the process terminated unexpectedly.”

When it appears there will not be any information recorded in the web logic logs as the Service Manager had failed to initiate web logic startup process itself. But we need to check the Windows Event logs for more information on this.

Soln:

 To start Web logic as a Windows service the Service Manager throws an exception – “Error 1067 the process terminated unexpectedly.”

When this happens there will not be  store any information recorded in the web logic logs as the Service Manager had failed to initiate web logic start-up process itself. But there we need to check the Windows Event logs for more information on this.