Escolar Documentos
Profissional Documentos
Cultura Documentos
Products
Products Industries
Industries Services and Support
Services Support Training
Training Community
Community Developer
Developer Partner
Partner About
About
Ask a Question Write a Blog Post Login
Tom Xing
January 29, 2015 2 minute read
At least, the system admin had better know which logs should be collected before the restart, so that we can grab a chance for RCA.
/* ‘Server hang’ is de nitely a gigantic topic – this blog will try not to dig into further technical details. */
https://blogs.sap.com/2015/01/29/as-java-system-hang-occurs/ 1/7
3/20/2019 “AS Java System hang occurs!” – What to do | SAP Blogs
Besides all above, screenshots / HTTP Watch trace are de nitely helpful.
These questions help you as well as SAP support to understand your problem.
https://blogs.sap.com/2015/01/29/as-java-system-hang-occurs/ 2/7
3/20/2019 “AS Java System hang occurs!” – What to do | SAP Blogs
– If dispatcher / ICM / server node has died -> don’t expect a normal behavior. Check work folder and defaultTrace.
– If issue only occurs on speci c client PC / browser -> check if browser is supported as per PAM. And check if this PC has any peculiarities against others.
– If issue only occurs on certain instance / server nodes -> check below steps agains that speci c instance / server node.
– If issue occurs on consumer portal under FPN scenario, also check the provider system.
– Last but not least, make sure there’s enough CPU/RAM/Disk resource on OS.
Regarding other scenarios, for simplicity, you can collect below trace together.
– Thread dump or SAP JVM Pro ler trace, on server node (and also dispatcher for 7.0X)
– work folder
– defaultTrace
https://blogs.sap.com/2015/01/29/as-java-system-hang-occurs/ 3/7
3/20/2019 “AS Java System hang occurs!” – What to do | SAP Blogs
/*
– Scenario 1
AS Java is running, responding, but some speci c application returned a blank page (browser is no longer loading the page). Other applications are working
ne.
-> Collect HTTP Watch trace so that we can see where it stopped.
– Scenario 2
AS Java is running, responding, but some speci c application did not respond and browser is still waiting. Other applications are working ne.
We must check where it actually hangs during HTTP tra c – it might be on AS Java, on AS ABAP, or on 3rd party system, or simply on network.
-> In this scenario, HTTP Watch trace will be necessary at very rst place.
– Scenario 3
https://blogs.sap.com/2015/01/29/as-java-system-hang-occurs/ 4/7
3/20/2019 “AS Java System hang occurs!” – What to do | SAP Blogs
AS Java is running but not responding. Or, it is refusing new requests but still serving the old ones.
It is very likely that (some speci c kind of) threads are exhausted, and we must check at runtime.
-> Collect thread dump or SAP JVM Pro ler trace when issue IS OCCURRING. This is necessary to tell the root cause.
*/
N.B., it’s not a guarantee that the logs listed above are 100% enough for every issue. But it’s a good start.
Reference Documents
https://blogs.sap.com/2015/01/29/as-java-system-hang-occurs/ 5/7
3/20/2019 “AS Java System hang occurs!” – What to do | SAP Blogs
Alert Moderator
Assigned tags
View more...
Java performance problem : the logs which needs to be collected for SAP Support
By Asha Pillai , Nov 14, 2014
Anatomy for SAP Net Weaver Administrator – Operations
By Former Member , Apr 09, 2014
Push ABAP system data to a Java only SLD ( NW 7.3 and Above)
By Former Member , Nov 12, 2014
Related Questions
https://blogs.sap.com/2015/01/29/as-java-system-hang-occurs/ 6/7
3/20/2019 “AS Java System hang occurs!” – What to do | SAP Blogs
2 Comments
Former Member
Like (0)
BR, Tom
Like (0)
Privacy Terms of Use Legal Disclosure Copyright Trademark Cookie Preferences Sitemap Newsletter
https://blogs.sap.com/2015/01/29/as-java-system-hang-occurs/ 7/7