Issues for Weblogic-2

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>
 [0R]
 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 in Cluster.

Server Down/Unknown Type:
Login to the Server through Putty/ Open the Admin Console

Check for the respective Instance Process from putty and also  the instance Status from Admin Console

If Processes does not exist and Instance Status is Unknown, check the logs of the Server Instance and Admin Logs.

Admin and managed server logs.

Node manage status.

Find the root Cause from the logs And Restart the required instances

If the URL is not working:

Need to the Status of the Server instances on which this Application is deployed.

next Default Queue threads or (Application Specified Queue if any)

1.If idle threads are zero or not. 

2.Then Server logs and Application logs (Out logs) for Errors and Exceptions.

 3.If idle threads are Zero, Check which Application is consuming all threads and if it is the same application which you are accessing, then check with the Application Owner.

 4.Need to restart the Corresponding Instances, need to check with  App owner why they are getting consumed

5.Check the Corresponding Connection pool and Datasource whether they are running fine or not.

Application errors:
Access the Application URL whether the instances and their status Errors

Check the logs of the Server as well as App(Out) logs

Check Connection pool Parameters and Datasource