2584370 - AS Java fails to start - core service [dbpool] failed to start - No space left on device

• Server nodes are not starting up. The following errors can be found in the dev_server and std_server files:

Service [dbpool] start ================= ERROR =================
CSN Component [BC-JAS-TRH], DC Name [sap.com/dbpool]
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:394)
at com.sap.engine.services.dbpool.PoolFrame.getComponentsPersistentFiles(PoolFrame.java:405)
at com.sap.engine.services.dbpool.PoolFrame.start(PoolFrame.java:140)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)
FATAL: Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [dbpool] failed to start]

• The following error can be found in the defaultTrace files:
  

Text: Error reading [...] file entry from [...] component [...] container
[EXCEPTION]
com.sap.engine.lib.config.api.exceptions.ClusterConfigurationException: The entry with the specified name <XML file> cannot be retrieved in <component>.
...
Caused by: java.io.IOException: No space left on device

SAP NetWeaver Application Server Java

KBA , BC-JAS-TRH , Transactions and Resource Handling , Problem