Exception occurred while loading _WL_TIMESTAMP FILE

Question

Hi all,
I have an application packaged in a EAR file, but when I deploy through the Weblogic Server Administration console, i get a strange error:
<Error> <EJB> <BEA-010003> <Exception occurred while loading WLTIMESTAMP FILE.
java.io.FileNotFoundException: /opt/bea/domains/bpm/servers/BPMServer/cache/EJBCompilerCache/1bscgreimm37w/_WL_GENERATED (Too many open files)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:106)
at weblogic.ejb.container.deployer.EJBDeployer.getFileHash(EJBDeployer.java:464)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:586)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1154)
Truncated. see log file for complete stacktrace
&gt;
java.lang.NullPointerException
at weblogic.utils.FileUtils.remove(FileUtils.java:274)
Searching over the Oracle/BEA documentation i found this :
BEA-010003 Error: Exception occurred while loading WLTIMESTAMP FILE.
Description Exception occurred while loading WLTIMESTAMP FILE. Forcing recompilation: ioException
Cause      The container generates WLGENERATED file, which stores the server version of the appc compiler. if the current server version is different from the version specified in WLGENERATED file, appc recompiles the beans. There was an error reading this file.
Action The container will automatically recompile the beans.
But if the container compiles the beans again, why in the deployments view, it doesn't work, and the application is never at Active state?
Any help is appreciated!
Thiago

Answer 1

Looking at your stack trace, I don't believe the issue is directly related to the WLTIMESTAMP file but rather it looks like you have hit the limit on the number of open file descriptors for your process (note that the stack trace says "Too many open files" immediately after reporting what file it failed to open). Looks like you either have an FD leak or your OS/shell limit on the number of open file descriptors allowed per process may be set too low for what you are trying to accomplish.