SAP Knowledge Base Article - Preview

1787073 - Slow start up of SAP Netweaver AS JAVA


The starting process of SAP Netweaver AS JAVA is very slow and the application server becomes unresponsive. To analyse a hanging situation 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;( at;)Ljava.lang.String;( at;)Ljava.lang.String;( - locked<0x455a1360> (a at;);( at;);( at;);( at;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;);( at;[;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;);( at;[;Ljava.lang.String;Ljava.lang.String;I[Ljava.lang.Object;Ljava.lang.Throwable;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;);( at;);("

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



  • Release Independent
  • SAP NetWeaver


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


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.