Troubleshooting Archive

Unable to start managed server from nodemanager

When we try to start the managed server from nodemanager, we get the following error.

<BEA-090064> <The DeployableAuthorizer “” returned an error: [Security:090310]Failed to create resource.>

This errror comes because the managed server ldap server (slave) is not in sync with the Admin Server ldap server ( master).

To overcome this issue we can use two very important configurations.


Refresh Replica at Startup and Master First.


master first


Master First ensures managed server always connect to the ldap server of the admin server.

Refresh Replica at startup ensures that whenever managed server is restarted, it takes the latest ldap data from the admin server.



High CPU Usage of WebLogic Server on Linux

If you observe CPU being hogged by the Weblogic Server process on a linux machine,
you need to find out the Weblogic Server process id using

ps -ef | grep java

After you’ve found out the process id, find the thread id’s ( light weight process id’s) and their CPU usage using top command.

top -H -p 2389 (Weblogic Server Process Id)


2703 , 2704 & 2705 are the light weight process that are hogging up the CPU.

We take thread dump using kill -3 2389 (Weblogic Server Process Id)

We can map the light weight process to Weblogic Server threads by converting 2703 to hex 0xa8f.

We search for the thread (nid=0xa8f) in the thread dump to know what the thread is doing.
From the stack we can make out some complex mathematical operation is going on.
Inorder to avoid the High CPU we need to change the code to simplify the operation.

“Thread-19” daemon prio=10 tid=0x8a092000 nid=0xa8f runnable [0x887fe000]
java.lang.Thread.State: RUNNABLE
at java.lang.StrictMath.pow(Native Method)
at java.lang.Math.pow(
at jsp_servlet.__index$
at while validating xml ParseError at [row,col]:[2,134]
Message: Tried all: ‘1’ addresses, but could not connect over HTTP to server: ‘’, port: ’80’

at weblogic.servlet.internal.TldCacheHelper$TldIOHelper.parseXML(
at weblogic.descriptor.DescriptorCache.parseXML(
at weblogic.servlet.internal.TldCacheHelper.parseTagLibraries(
at weblogic.servlet.internal.War.getTagInfo(
at weblogic.servlet.internal.WebAppServletContext$ServletContextWebAppHelper.getTldInfo(

You might encounter the following exception when the server on which Weblogic is hosted is not able to communicate to internet.The reason being that internet access is allowed only via proxy.
To allow access we need to pass on the proxy details as a JVM Option.

-Dhttp.proxyHost=< proxy host> -Dhttp.proxyPort=

This should resolve the issue.

You can test the connection by a simple jsp that makes a URL Connection

System.setProperty(“http.proxyHost”, “proxy host”);
System.setProperty(“http.proxyPort”, “proxy port”);
URL url = new URL(“”);