SAP Knowledge Base Article - Preview

1787073 - Slow start up of SAP Netweaver AS JAVA

Symptom

The starting process of SAP Netweaver AS JAVA is very slow and the application server becomes unresponsive. To analyse a hanging siutation we recommend to take thread dumps on the system: How to get a full thread dump in AS Java.

In thread dumps, you have noticed that logging components take many threads:

"at java.lang.StringBuilder.toString()Ljava.lang.String;(StringBuilder.java:444) at com.sap.tc.logging.ListFormatter.format(Lcom.sap.tc.logging.LogRecord;)Ljava.lang.String;(ListFormatter.java:438) at com.sap.tc.logging.Log.writeInt(Lcom.sap.tc.logging.LogRecord;)Ljava.lang.String;(Log.java:842) - locked<0x455a1360> (a com.sap.tc.logging.FileLog) at com.sap.tc.logging.Log.writeInternalByAPI(Lcom.sap.tc.logging.LogRecord;)Lcom.sap.tc.logging.LogRecord;(Log.java:908) at com.sap.tc.logging.LogController.writeToLogs(Ljava.util.CollectionLcom.sap.tc.logging.LogRecord;)Lcom.sap.tc.logging.LogRecord;(LogController.java:3085) at com.sap.tc.logging.LogController.messageInternal(Lcom.sap.tc.logging.LogRecord;)Lcom.sap.tc.logging.LogRecord;(LogController.java:2104) at com.sap.tc.logging.LogController.prepareLogRecord(Lcom.sap.tc.logging.LogRecord;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Lcom.sap.tc.logging.LogRecord;(LogController.java:2203) at com.sap.tc.logging.LogController.logTInt(ILcom.sap.tc.logging.LogController;[Lcom.sap.tc.logging.LogController;Ljava.lang.String;Ljava.lang.String;I[Ljava.lang.Object;Ljava.lang.Throwable;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String Ljava.lang.String;)Lcom.sap.tc.logging.LogRecord;(LogController.java:2262) at com.sap.tc.logging.LogController.logTInt(ILcom.sap.tc.logging.LogController;[Lcom.sap.tc.logging.LogController;Ljava.lang.String;Ljava.lang.String;I[Ljava.lang.Object;Ljava.lang.Throwable;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Lcom.sap.tc.logging.LogRecord;(LogController.java:2236) at com.sap.tc.logging.Location.pathT(Ljava.lang.String;)Lcom.sap.tc.logging.LogRecord;(Location.java:4114)"

This can result in the system hanging in the starting framework or starting applications phase of the startup.


Read more...

Environment

  • Release Independent
  • SAP NetWeaver

Product

SAP NetWeaver Application Server for Java all versions ; SAP NetWeaver all versions

Keywords

Debug, Logging API, Trace severity, info, starting framework, stuck, hanging, applications , KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-JAS-ADM-ADM , Administration , BC-JAS-ADM-LOG , Logging , Problem

About this page

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

Search for additional results

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