1956911 - Long startup after portal upgrade to Netweaver 7.3X

Symptom

After upgrading the Netweaver portal from version 7.0x to 7.3x or just updating to a higher SPS, in some cases it was observed that the Java instance is taking several hours to start and achieve running state, whereas it used to take 10-20 minutes before the upgrade.

Thread dumps on the server node will reveal these long running PCD threads, found in the work/std_server0.out or dev_server0 logs:

application="sap.com/com.sap.portal.importlistenersmonitor"

...

java.lang.Thread.State: RUNNABLE

    at java.net.SocketInputStream.socketRead0(Ljava/io/FileDescriptor;[
BIII)I(Native Method)
    at
java.net.SocketInputStream.read([BII)I(SocketInputStream.java:129)
    - additional info (remote: prtdq/199.12.225.18:1527, local:localhost/127.0.0.1:63793)

...

- locked <0x000000002b5a3f50> (a oracle.jdbc.driver.T4CConnection)

....

- locked <0x000000000d475d98> (a com.sapportals.portal.pcd.gl.xfs.XfsList)

....

- locked <0x000000000d47c388> (a com.sapportals.portal.pcd.gl.xfs.XfsDeltaLink)

Environment

SAP NetWeaver Application Server Java

Product

SAP NetWeaver 7.3 ; SAP NetWeaver Application Server 7.0 ; SAP NetWeaver Application Server 7.01 ; SAP NetWeaver Application Server 7.02 ; SAP enhancement package 1 for SAP NetWeaver 7.3

Keywords

PCD, long startup , KBA , BC-JAS-SF , Startup Framework , BC-PIN-PCD , PCD Generic Layer Services , 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.