Working with ".Lok" files in Weblogic server

ERROR:

ERROR: <BEA-141281> <unable to get file lock, will retry …> 

Or 

<2017-3-22 five eight in the afternoon of 22 seconds CST> <Info> <Management> <BEA-141281> <unable to get file lock, will retry …> 

<2017-3-22 five eight in the afternoon of 40 seconds CST> <Info> <Management> <BEA-141281> <unable to get file lock, will retry …>

Solution is  to Delete  the *.lok files  from below location after that Server restarted is mandatory .

file locations are 

Access to domain_home:

cd /Oracle/Middleware/user_projects/domains/idm_domain

Edit.lok file will be deleted

rm edit.lok

Remove the 2 config.lok

Access to domain_home/config:

cd /Oracle/Middleware/user_projects/domains/idm_domain/config/

Config.lok file will be deleted

rm config.lok

Remove the 3 AdminServer.lok

cd  /Oracle/Middleware/user_projects/domains/idm_domain/servers/AdminServer/tmp

rm AdminServer.lok

Remove the 4 EmbeddedLDAP.lok

/Oracle/Middleware/user_projects/domains/idm_domain/servers/AdminServer/data/ldap/ldapfiles

rm EmbeddedLDAP.lok

Two delete the *.DAT file under the Domain:

Access to the domain_home

cd /Oracle/Middleware/user_projects/domains/idm_domain

Find the file was deleted

[oracle@idm idm_domain]$ find servers/ -name "*.DAT" 

servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT 

servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT

Restart Weblogic,

Track the Changes through Admin Console

In Production , some times we need  to track all admin console level changes for Audit and debug the changes.

This can be done with below step of changes

How to do it...
Carry out the following steps to protect the configuration changes:
1. Access the Administration Console with your web browser at http://prod01.domain.local:7001/console.
2. Click on the Preferences link.
3. Enable the following checkboxes:
Show Advanced Sections
Warn If User Holds Lock
Warn User Before Taking Lock
4. Click on the Save button.
5. Open the WLST Script Recording tab.
6. Enable the following checkboxes:
Append to File
Automatic Recording
7. Click on the Save button.
8. Obtain the configuration lock by clicking on Lock & Edit.
9. Click the PROD_DOMAIN link on the Domain Structure on the left.
10. Choose Change Log and Audit in the Configuration Audit Type drop-down menu.
11. Enable the Configuration Archive Enabled checkbox.
12. Set the number of back files in the Archive Configuration Count text field. Type 250
      as the value. The default value is 50.
13. Click on the Save button.
14. Activate the changes by clicking on the Activate Changes button.
15. You will have to restart the Administration Server for the changes to take effect.

Thanks
Babu

Protect Chnages in Administractor Changes @ Weblogic Server 12c

This is very important as Part of Administration task . Why because we need to track all admin changes, fail over and all other users changes should be logged.


Change management in a production environment is critical and has to be done with careful
preparation and planning. WebLogic provides a way to save and later track all the changes
made in its configuration.

This recipe focuses on how to enable the embedded configuration backup, how to enable
the configuration changes audit, and how to automatically record a Jython script to all the
changes made in the Administration Console that can be used later with WLST.

Common Issues with WL @ Prod Env

Common Issues with Weblogic Server @ Production Environments

• 1.       Application URL is not accessible.
• 2.       Application responding very slowly.
• 3.       Server state is down.
• 4.       Server state is crashed.
• 5.       Server state is hanging.
• 6.       All Database Exceptions.
• 7.       Connection pool closed issues.
• 8.       Disk Space issues.
• 9.       Application Deployment Issues.
• 10.   File not found exceptions.
• 11.   Out of memory Exception.
• 12.   Heap out of memory
• 13.   Perm gen space error
• 14.   Null pointer exception.
• 15.   Struck thread in Servers
• 16.   High CPU utilization.
• 17.   Socket exceptions.
• 18.   Unable to read data from socket.
• 19.   Too many open files exception.
• 20.   Performance issues.
• 21.   Port or listen address already in used exception.
• 22.   Socket already in used exception.
• 23.   Proxy server exceptions
• 24.   Node manager bind exception.
• 25.   Authentication and Authorization. 

Thanks,

Babu

BEA & Oracle Product Support Info for weblogic Server

Regards,
Babu

Administering Managed Server With Node Manager

Regards,

Babu

Script for Start, Stop, Status and Restart of Tomcat Server

Below script can be used for stop, start, restart and status checking. Change installed path according to environment.

#!/bin/ksh

export BASE=/home/programs/Servers/jakarta-tomcat-6.0.36/bin

prog=jakarta-tomcat-6.0.36

stat() {

if [ `ps auxwwww|grep $prog|grep -v grep|wc -l` -gt 0 ]

then

echo Tomcat is currently running.

else

echo Tomcat is currently not running.

fi

}

case "$1" in

start)

if [ `ps auxwwww|grep $prog|grep -v grep|wc -l` -gt 0 ]

then

echo Tomcat seems to be running. Use the restart option.

else

$BASE/startup.sh 2>&1 > /dev/null

fi

stat

;;

stop)

$BASE/shutdown.sh 2>&1 > /dev/null

if [ `ps auxwwww|grep $prog|grep -v grep|wc -l` -gt 0 ]

then

for pid in `ps auxwww|grep $prog|grep -v grep|tr -s ' '|cut -d ' ' -f2`

do

kill -9 $pid 2>&1 > /dev/null

done

fi

stat

;;

restart)

if [ `ps auxwwww|grep $prog|grep -v grep|wc -l` -gt 0 ]

then

for pid in `ps auxwww|grep $prog|grep -v grep|tr -s ' '|cut -d ' ' -f2`

do

kill -9 $pid 2>&1 > /dev/null

done

fi

$BASE/startup.sh 2>&1 > /dev/null

stat

;;

status)

stat

;;

*)

echo "Usage: tomcat start|stop|restart|status"

esac

Thanks,

Babu