LAKSHMI WEBLOGIC/SOA ADMIN

JDBC: Problem Overview: Stale database connections in WebLogic occur when connections remain open but are no longer in use by applications. This leads to: High CPU usage  (database server struggles with managing dead connections) High memory consumption  (each idle connection consumes resources) Database breakdown  (connection pool exhaustion leading to "ORA-00020: maximum number of processes exceeded" or similar errors) Root Causes: Improper Connection Handling Missing  connection.close()  in application code (JDBC leaks) T ransactions left open without commit/rollback JDBC Pool Misconfiguration Missing  TestConnectionsOnReserve  or  InactiveConnectionTimeout Overly large  MaxCapacity  with no proper cleanup Network/DB Failures Database restarts or network drops leaving connections in a zombie state Long-Running Queries Queries that hang indefinitely (e.g., due to locks or bad SQL) Detection Methods: WebLogic Console Checks Navigat...

The solution for Log files not rotating   Check the Status of the Server ./startWeblogic.sh ./startManagedWeblogic.sh <manageservername> Another option: Check in the console. Check the disk Space(if fit is full, Delete the logs and then  restart the Server) du –kh (folder) df –kh (filesystem) If the avail capacity is  45% 90% If full , mv <source > <destination> Delete, rm –rf <filename: adminserver.log> Major Server Errors: Check the Status of Servers. ./startWeblogic.sh ./startManagedWeblogic.sh <manageservername> Need to do from console. Check the Server logs /apps/bea/domain/gwmp_destop/logs Adminserver.log Managedserver.log For this Database Errors, Check the Connection pool and Datasource. Services->jdbc->connectionpool,datasource Check out the Deployment Descriptors. Weblogic.xml,web.xml Based on the logs we can change Configuration Changes, Make the Changes and then restart instances one by one if...

Server Lifecycle Management: # Start Admin Server $DOMAIN_HOME/startWebLogic.sh  # Unix %DOMAIN_HOME%\startWebLogic.cmd  # Windows # Start Managed Server $DOMAIN_HOME/bin/startManagedWebLogic.sh <server_name> <admin_url> # Graceful stop $DOMAIN_HOME/bin/stopWebLogic.sh  # Admin $DOMAIN_HOME/bin/stopManagedWebLogic.sh <server_name> t3://admin_host:port Force Kill (if hung): kill -9 $(pgrep -f "weblogic.Name=<server_name>")  # Unix taskkill /F /PID <pid>  # Windows Deployment Commands: WLST (WebLogic Scripting Tool): # Deploy app deploy('my_app', '/path/to/app.ear', targets='AdminServer') # List deployments ls('/AppDeployments') # Undeploy undeploy('my_app', targets='AdminServer') Command-Line (weblogic.Deployer): java weblogic.Deployer -adminurl t3://localhost:7001 -deploy /path/app.war Log Inspection: Tail Logs in Real-Time tail -f $DOMAIN_HOME/servers/AdminServer/logs/AdminServer.log Search for Er...