SAP Knowledge Base Article - Preview

3254961 - AS Java startup takes long time by "Starting apps" startup phase after upgrade - Deploy Read AppBinaries Thread

Symptom

After upgrading your AS Java system, first startup might take much longer than expected. It may take couple of hours.

dev_server files show most of the elapsed time by:

[...]
State changed from 2 (Starting framework) to 10 (Starting apps)
[...]

Thread dumps show:

[...]
Deploy Read AppBinaries Thread <x>
[...]
J java.lang.Thread.State: RUNNABLE
J at java.io.FileOutputStream.open(Ljava/lang/String;Z)V(Native Method)
J at java.io.FileOutputStream.<init>(Ljava/io/File;Z)V(FileOutputStream.java:201)
J at java.io.FileOutputStream.<init>(Ljava/io/File;)V(FileOutputStream.java:151)
[...]


Read more...

Environment

SAP NetWeaver Application Server Java all versions

Product

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

Keywords

KBA , BC-JAS-SF , Startup Framework , BC-JAS-DPL , Deployment , 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.