weblogic error


Wednesday, April 15, 2015

Weblogic domain creation error “Unable to invoke parse in InvokeStaticMethodTask”

While creating weblogic domain on linux server below error is encountered.
Steps:export WLS_HOME=/opt/apps/Oracle/Middlewareexport WLS_SERVER=/opt/apps/Oracle/Middleware/wlserver_10.3export ORACLE_HOME=/opt/apps/Oracle/Middleware/Oracle_SOA1export JAVA_HOME=/opt/apps/Java6/jdk1.6.0_20export WLS_DOMAIN=/opt/apps/Oracle/Middleware/user_projects/domainscd $ORACLE_HOME/common/bin./config.sh

Here is the full stack trace of the error.
2010-08-02 09:56:28,142 ERROR [invokeStaticMethod] com.bea.plateng.wizard.silent.tasks.InvokeStaticMethodTask – Unable to invoke parse on class com.bea.plateng.plugin.PlugInExecutionPlanParser>java.lang.reflect.InvocationTargetExceptionat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)at java.lang.reflect.Method.invoke(Method.java:597)at com.bea.plateng.wizard.silent.tasks.InvokeStaticMethodTask.execute(InvokeStaticMethodTask.java:304)at com.bea.plateng.wizard.silent.tasks.AbstractSilentTask.run(AbstractSilentTask.java:28)at java.lang.Thread.run(Thread.java:619)Caused by: java.lang.NullPointerExceptionat java.io.FileInputStream.<init>(FileInputStream.java:103)at java.io.FileInputStream.<init>(FileInputStream.java:66)at com.bea.plateng.plugin.PlugInExecutionPlanParser.parse(PlugInExecutionPlanParser.java:111)at com.bea.plateng.plugin.PlugInExecutionPlanParser.parse(PlugInExecutionPlanParser.java:90)… 7 more2010-08-02 09:56:28,145 ERROR [invokeStaticMethod] com.bea.plateng.wizard.silent.tasks.InvokeStaticMethodTask – parameterValue 0 = <null>
The problem is the classpath for launching the configuration wizard.
The source of this classpath entry is from $WLS_HOME/common/bin/commEnv.sh
The highlighted entry is invalid. It should point to 10.3 and not Once this is changed the Configuration Wizard can be launched successfully for domain creationPosted by RamsSon..(”’)(”’) at 2:06 AMNo comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest

Weblogic Managed Server goes down with java.lang.OutOfMemoryError: Java heap space

This is a short post covering how to set heap space in weblogic server(10.3.2) . Incase the weblogic managed server goes down with java.lang.OutOfMemoryError: Java heap space or java.lang.OutOfMemoryError: GC overhead limit exceeded you need to increase the heap space settings.
Modify the below file to increase the heap space.$MW_HOME/user_projects/domains/domain_name/bin/setDomainEnv.sh
Add the environment variable USER_MEM_ARGSUSER_MEM_ARGS=”-Xms4G -Xmx8G -XX:PermSize=256m -XX:MaxPermSize=512m”export USER_MEM_ARGSSetting this variable overwrites any default java memory arguments passed during startup.Once done restart the admin and managed servers for the change to take effect.
For starting admin server :

$MW_HOME/user_projects/domains/domain_name/bin/startWebLogic.shFor starting managed server:
$MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.shPosted by RamsSon..(”’)(”’) at 1:57 AMNo comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest

Weblogic Server Monitoring using command line options

There maybe a requirement to monitor the weblogic admin and managed servers using some cron jobs rather than having to manually monitor the Admin console and see if they are running. A robust shell script can be created which basically checks for the server status, or does a ping to the URLs to see if they are active and incase of discrepancies sends out an email to the admin/support group.
The various command line options which can be included in the script are:
1. First and foremost we can check at the unix level if the server processes are running using command ps -ef| grep “weblogic” .This should ideally return us 3 processes(assuming we have services running under one domain) : nodemanager, admin server, managed server (weblogic.NodeManager, -Dweblogic.Name=soa_server1, -Dweblogic.Name=AdminServer)So we can grep and check if any of these are down/missing.
2. The other way to check if processes related to weblogic are running is by making use of weblogic.Admin command line utility,
cd <MW_HOME>/wlserver_10.3/server/bin. ./setWLSEnv.sh
NOTE: There are two Dots before the Script separated by a Single Space… First Dot represents that set the environment in the Current Shell….and Second Dot represents that pick the Script from current Directory
Once environment has been set you can run below commands:java weblogic.Admin -username weblogic -password welcome1 GETSTATE AdminServerCurrent state of “AdminServer” : RUNNINGjava weblogic.Admin -username weblogic -password welcome1 GETSTATE soa_server1Current state of “soa_server1” : RUNNING
3. We can also do a ping to the host (admin and managed servers) to make sure they are alive. Many times it may happen that the servers are just hung, so we can use “weblogic.Admin” command line utility to do a weblogic PING.
java weblogic.Admin -url adminserverhost:port -username weblogic -password welcome1 PING 10
Sending 10 pings of 100 bytes.RTT = ~1020 milliseconds, or ~102 milliseconds/packetIf it is alive and returns good, then we are good.
4. There maybe cases where the Weblogic servers may go down due to FMW database being down (soainfra down) or due to heap space/outofmemory errors. In those cases the shell script can check into the log file <MW_HOME>/user_projects/domains/<domain_name>/servers/soa_server1/logs/soa_server-diagnostic.log and see if any of the below error messages are present.
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor (This comes when FMW DB is down)java.lang.OutOfMemoryError: Java heap space (This comes when the heapspace of server is exceeded)
java.lang.OutOfMemoryError: GC overhead limit exceeded (This again is related to heapspace of server)

NOTE: This is not a complete list but few errors which show up in log files due to WLS infrastructure issues. These errors will cause the BPEL/composites to fault and give unexpected results. Hence pro-actively monitoring these will help in fixing them soon.Posted by RamsSon..(”’)(”’) at 1:49 AMNo comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest

SOA 11g : EM Console fails with HTTP 404 error ; JspServlet error

After restarting servers (admin and managed) found that EM console isn’t coming up and it shows below error either on browser or Admin server log files:
“JspServlet error: Servlet unable to dispatch to the following requested page: java.io.FileNotFoundException: /targetauth/asLogin.jspx”On further checking the directory targetauth was missing from <MW_HOME>/user_projects/domains/<domain_name>/servers/AdminServer/tmp/_WL_user/emcore/28c293 location. This directory has the asLogin.jspx file.
You can copy this directory from a different domain but that would still give errors like”JspServlet error: Servlet unable to dispatch to the following requested page: java.io.FileNotFoundException: MDS-00013: no metadata found for metadata object “/targetauth/asLogin.jspx”
Solution :1. Stop the Admin server2. Rename <MW_HOME>/user_projects/domains/<domain_name>/servers/AdminServer/tmp/ directory to tmp-old3. Restart the Admin server. The tmp directory will be recreated again.
Open EM Console.It should work now !


About Author

Leave A Reply