NWA does not respond

[vadimklimov]

Dear SAP specialists,

I'm currently executing post-installation activities for SAP PI usage type on SAP NetWeaver 7.0 (OS: MS Windows Server 2003, DBMS: MS SQL Server 2005).

When using NetWeaver Administrator and running Template Installer, the system hangs and does not respond from time to time. J2EE instance is up and running, J2EE processes are green in SAP MMC. When NWA hangs, it is not possible to re-connect to it (no response), it is also not possible to connect to the instance via Visual Administrator.

The step during which NWA hangs is not some specific one: NWA hangs during execution of random steps included in PI scenario of installer.

After restarting J2EE instance, the issue appears after some time. Restart of the server also ddin't solve the issue.

Could you please advise where to proceed with investigation and what should be checked?

My best regards,

Vadim

[Former Member]

Hi

you can check the trace or log flies in work direcotry..

check table spaces and SM21 logs, growth of the system.

helpful,

https://cw.sdn.sap.com/cw/docs/DOC-105430

regards

nagaraju

[vadimklimov]

Dear Nagaraju,

Let me thank you for the response.

Trace files of J2EE processes do not contain any exceptions or process terninations, J2EE processes themselves are also running well (they all are in healthy state in SAP MMC).

System logs in ABAP instance are error-free as well.

Regarding tablespaces... This is a new installation and database is not loaded (there is a lot of free space available for the database).

I have overcome the issue by manual execution of steps contained in NWA Template Installer, but I haven't yet found the root cause of such hangings appearing during NWA Template Installer usage.

Vadim

[Former Member]

Hello,

When the /nwa hangs, are you able to open another browser session with just J2EE homepage /index.html ?

Also, please check the MaxThreadCount for the ApplicationThreadManager in Server process using the Confgitool. Please make them 150 or higher and restart the instance.

If that doesn't resolve, please replicate the issue and take 5 threaddumps as per note 710154 during the hang, on the server

process. The threaddumps should be taken at an interval each. Then, please open the threaddumps(on non-ibm systems they are written to std_server.out file else javacore.txt files) using the threaddump viewer. You can look for the free application threads or thread exhaustion and blockage. The threaddump viewer is explained her:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2015bb75-a9da-2910-e0b1-c5ba9fe90...

Hope the above helps.

Regards,

Snehal

SAP Labs, Palo Alto, CA(USA)