troubleshooting Archive 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(“”);

NodeManager issues during oracle weblogic server environment setup

I/O error while reading domain directory: Domain directory ‘D:\bea\wlserver_10.3\common\nodemanager’ invalid (domain salt file not found

We need to to nmEnroll and restart the nodemanager to fix this error.

weblogic.nodemanager.common.ConfigException: Native version is enabled but node manager native library could not be loaded

You need to set the LD_LIBRARY_PATH for Solaris/Linux and SHLIB_PATH for HP-UX



Fatal error in node manager server
at weblogic.nodemanager.server.ServerManager.getStartCallbacks(
at weblogic.nodemanager.server.AbstractServerManager.initialize(
at weblogic.nodemanager.server.AbstractServerManager.(

This is a bug on WLS and there is a patch available for this.
Please contact Oracle Customer Support.

Troubleshooting too many open files issues

Servlet failed with IOException many open files)
at Method)
at weblogic.utils.classloaders.FileSource.getInputStream(
at weblogic.servlet.internal.WarSource.getInputStream(
at weblogic.servlet.FileServlet.sendFile(

In this post i’ll try to give some general guidelines on how to go about troubleshooting Too many open files exception

File descriptors are handles used by a process to identify an open file.
Too many open files exception is thrown when a particular process runs out of File Descriptors.
To troubleshoot it we need to first check the file descriptor limits.

It is logged in the server logs

Then check the max fd’s available.

cat /proc/sys/fs/file-max

Get the list of files opened

lsof –p

Get the count

lsof –p | wc –l

Check if the system has enough FD’s and what percentage of available FD’s are being used by the process.
Check with the developers whether those files should be opened at that time or not.

Increasing the File Descriptor limit can be a temporary work around.

ulimit -n 65535