SAP Knowledge Base Article - Preview

2075671 - Best Practice: How to identify Tomcat crash, unresponsive or hanging issue


How to identify Tomcat crash or unresponding issue.



  • SAP BusinessObjects BI Platform 4.x
  • Tomcat7
  • Tomcat 8, Tomcat9 (Only applicable to Scenario 5 & 6 because MaxPermSize is no longer used from Tomcat8, 2297866)


JVM heap, apache tomcat, hanging, out of memory, java heap size, fatal error, VM Arguments, EXCEPTION_ACCESS_VIOLATION, stop, start, JMX, HTTP-NIO, HTTP-NIO-8080, HTTP-NIO-8080-EXEC, 4.1, 4.2, 4.3 , KBA , tomcat , crash , hang , bidep , bpkba , tskba , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.