cancel
Showing results for 
Search instead for 
Did you mean: 

MaxThreadCount and server0 failure in portal

Vivek_Hegde
Active Contributor
0 Kudos

Hello All,

Can somebody give more detaisl on relevency of server0 node failure to MaxThreadCount of a Java Engine?

Recently we had an issue where the portal took very long time to load eventhough all the java processes were running.

Somebody mentioned me this might be due to threads. Can someone of you throw more lights on this topic?

Regards

Vivek Hegde

Accepted Solutions (1)

Accepted Solutions (1)

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

The Heap size and the max thread counts you will be using should be in co-relation (ie.e for maximum threads the more heap size required. Additional extra heap size will be on safer side) else it will definitely overload while processing too many threads at a time on server. This may result in sudden break-down. In Production environment it would involve risk and lead to re-start the J2Ee engine.

Well for me I will prefer to look into SAP help

http://help.sap.com/saphelp_nw04/helpdata/en/2d/e312403dbedd5fe10000000a155106/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/2d/12243ee9399a0be10000000a114084/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/29/84343e8c7f6329e10000000a114084/content.htm

Thanks

Sunny

Former Member
0 Kudos

HI Vivek,

This situation is due to memory exhaustion. this problem comes normally for cluster systems, additional server node

configurations etc.

we need to check whether the problem is really due to application thread exhausion or not using the following:

you can not open visual administrator, it will stuck at 99 %, if it is cluster login using another instance and drill down the effected server node.

server0> services> monitoring, right hand side expand kernel--> application thread pool and click on active thead count

if active thread account = maximum thread pool size , you can see red button i.e application threads are exhausted

restarting of the effected server node, will be the tempirary wok around to free up the active thread account.

permanent work around can be increasing the maximum thread pool according to the heap memory in the server.

Thanks and regards

Purna

Answers (1)

Answers (1)

former_member227283
Active Contributor
0 Kudos

Hi Vivek,

There could be many reason behind Slow starting of java application for e.g heavy memory usage.

For getting it into more detail , if possible generate same scenario again and share the STD_SERVER0.out log in forum.

Thanks

Anil