Recently I am working on installing Oralce Fusion middleware products which require WebLogic Application Server.
During start/stop Weblogic Application Server, we have to manually entering the username and password.To try to avoid doing this, we can add boot.properties file in security directory
1) go to server instance security directory, for example, ${Weblogic_Home}/user_projects/domains/testdomain/servers/AdminServer/security.
Note: must be server instance directory, if the boot.properties created at other directory, it will not work.
2) create a file named boot.properties as following:
username=weblogic
password=123456789
Note: no single or double quote for the values, or it will not work
Saturday, February 25, 2012
WebSphere launchClient.sh shows Out Of Memory Error.
One of my applications is using WebSphere Application Server launchClient script to run some functions.However, launchClient script can not be run properly because of the Out of memory issue(PermGen Space).
Checking WAS instance SystemOut.log and verbose gc logs,and no any errors in the log files, which shows launchClient script did not interact with the WAS instance yet.
solution:
add the options "-JVMOptions" to specify the perm size value
launchClient.sh -profileName AppSrv01 -JVMOptions "-XX:MaxPermSize=256M"
then the issue was solved.
Checking WAS instance SystemOut.log and verbose gc logs,and no any errors in the log files, which shows launchClient script did not interact with the WAS instance yet.
solution:
add the options "-JVMOptions" to specify the perm size value
launchClient.sh -profileName AppSrv01 -JVMOptions "-XX:MaxPermSize=256M"
then the issue was solved.
Subscribe to:
Posts (Atom)