SAP Knowledge Base Article - Preview

1987576 - com.sap.tc.logging.LogController: Configtool crashes due to file system space exhaustion

Symptom

  • When starting the configtool, after confirming that you want to use the default DB connection settings, the configtool crashes and an exception with a very large stack trace is written to the console
  • The stack trace is so large that it takes some moments to cease writing and when it is complete the portion of the stack trace visible in the console looks as follows:

        at com.sap.tc.logging.LogController.logTInt(LogController.java:2374)
        at com.sap.tc.logging.LogController.logSeverityTInt(LogController.java:2418)
        at com.sap.tc.logging.LogController.logSeverityTInt(LogController.java:2404)
        at com.sap.tc.logging.Category.warningT(Category.java:1616)
        at com.sap.tc.logging.Log.flush(Log.java:594)
        at com.sap.tc.logging.Log.writeInternalByAPI(Log.java:953)
        at com.sap.tc.logging.LogController.writeToLogs(LogController.java:3173)
        at com.sap.tc.logging.LogController.messageInternal(LogController.java:2290)
        at com.sap.tc.logging.LogController.logTInt(LogController.java:2374)
        at com.sap.tc.logging.LogController.logSeverityTInt(LogController.java:2418)
        at com.sap.tc.logging.LogController.logSeverityTInt(LogController.java:2404)
        at com.sap.tc.logging.Category.warningT(Category.java:1616)
        at com.sap.tc.logging.Log.flush(Log.java:594)
        at com.sap.tc.logging.Log.writeInternalByAPI(Log.java:953)
        at com.sap.tc.logging.LogController.writeToLogs(LogController.java:3173)
        at com.sap.tc.logging.LogController.messageInternal(LogController.java:2290)
        at com.sap.tc.logging.LogController.logTInt(LogController.java:2374)
        at com.sap.tc.logging.LogController.logSeverityTInt(LogController.java:2418)
        at com.sap.tc.logging.LogController.logSeverityTInt(LogController.java:2404)
        at com.sap.tc.logging.Category.logT(Category.java:463)
        at com.sap.engine.core.configuration.impl.Logging.log(Logging.java:100)
        at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationMan
agerBootstrapImpl.java:218)
        at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationM
anagerBootstrapImpl.java:49)
        at com.sap.engine.configtool.visual.ConfigTool.loadClusterData(ConfigTool.java:153)
        at com.sap.engine.configtool.visual.ConfigTool.initScan(ConfigTool.java:135)
        at com.sap.engine.configtool.visual.ConfigTool.<init>(ConfigTool.java:124)
        at com.sap.engine.configtool.visual.ConfigTool.main(ConfigTool.java:1176)
        ... 5 more
Program terminated abnormally
Press any key to continue . . .

  • The same issue occurs when you attempt to start the offline configuration editor

Read more...

Environment

  • Release Independent
  • SAP NetWeaver

Product

SAP Composition Environment all versions ; SAP NetWeaver all versions ; SAP Process Integration all versions ; SAP Solution Manager all versions

Keywords

Configtool crashes, com.sap.tc.logging.LogController, file system space exhaustion , KBA , BC-JAS-ADM-ADM , Administration , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.