SAP Knowledge Base Article - Preview

2794009 - Tomcat SAPJVM crashes in function xmlStream::va_tag

Symptom

  • After a period of time, Tomcat crashes and generates a hs_err_pid file to <BOBJINSTALLDIR>\Tomcat containing the following information:

    # A fatal error has been detected by the SAP Java Virtual Machine:
    #
    # SIGSEGV (0xb) at pc=0x00002b4371cf8353, pid=23092, tid=47570358150912
    # accessing faulting address: 0x00002b4300000000
    #
    # JRE version: Java(TM) SE Runtime Environment (8.0_131) (build 8.1.030)
    # Java VM: SAP Java Server VM (8.1.030 25.51-b02 Apr 26 2017 16:01:22 - 81_REL - optU - linux amd64 - 6 - bas2:288514 (mixed mode) compressed oops)
    # Problematic frame:
    # V [libjvm.so+0x10a4353] xmlStream::va_tag(bool, char const*, __va_list_tag*)+0x43 (sp=0x00002b43d64c8880) (pc=0x00002b4371cf8353)

  • In the OS logs, the following error is seen:
    SAPJVM[29545]:    :    [47351015171840]    15:04:39 ***ERROR (:0): OutOfMemoryError: Could not allocate 0 bytes

  • In the Tomcat logs (Stderr.log or Catalina.log), the following message is seen:

    java.lang.OutOfMemoryError: Metaspace
    Dumping heap to java_pid29545.hprof ...
    Heap dump file created [2924857359 bytes in 29.637 secs]


Read more...

Environment

  • SAP BusinessObjects Business Intelligence Platform 4.x
  • Tomcat 8 and above
  • SAPJVM
  • Windows
  • Linux / Unix

Product

SAP BusinessObjects Business Intelligence platform 4.2

Keywords

KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , 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.