Empty Config-Root In Deployment Plan Caused The Usage Of some TB Of Storage In_WL_TEMP_APP_DOWNLOADS

(Doc ID 2298020.1)

Last updated on OCTOBER 04, 2017

Applies to:

Oracle WebLogic Server - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

Customer experience a major and unexpected usage of storage space. 

 Checking in the domain filesystem for this middleware domain, the space was consumed by the following directory:

21T ./servers

21T ./servers/AdminServer

21T ./servers/AdminServer/tmp

21T ./servers/AdminServer/tmp/_WL_TEMP_APP_DOWNLOADS

 

Running out of space has caused that WebLogic Server crahsed and the log files reports following errorr message: 

####<Apr 30, 2017 1:31:56 PM CEST> <Error> <NodeManager> <wls_server1> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <6624be62-72f6-412f-97e9-65de78abd52d-0003d66b> <1493551916128> <BEA-300040> <An I/O error occurred while writing a NodeManager status change message.

java.io.IOException: No space left on device

at java.io.UnixFileSystem.createFileExclusively(Native Method)

at java.io.File.createTempFile(File.java:2001)

at weblogic.nodemanager.util.ConcurrentUnixFile.write(ConcurrentUnixFile.java:38)

at weblogic.nodemanager.common.StateInfoWriter.writeStateInfo(StateInfoWriter.java:46)

at weblogic.nodemanager.common.StateInfo.save(StateInfo.java:184)

at weblogic.nodemanager.NMService.writeStateInfo(NMService.java:271)

at weblogic.nodemanager.NMService.access$1000(NMService.java:61)

at weblogic.nodemanager.NMService$ServerRuntimePropertyChangeListener.propertyChange(NMService.java:348)

at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335)

at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:327)

at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263)

at weblogic.management.runtime.RuntimeMBeanDelegate._postSet(RuntimeMBeanDelegate.java:383)

at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:415)

at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:231)

at weblogic.t3.srvr.T3Srvr.failed(T3Srvr.java:248)

at weblogic.health.HealthMonitorService.timerExpired(HealthMonitorService.java:286)

at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:304)

at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:553)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)

 

Changes

 A new application has been deployed with a 'plan.xml' file where the <config-root> element is empty. 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms