SAP Knowledge Base Article - Preview

1906557 - Tomcat crash due to EXCEPTION_ACCESS_VIOLATION in the zip.dll with Java_java_util_zip_ZipEntry_initFields

Symptom

  • Periodically Tomcat is crashing and needs to be restarted to continue normal operations.
  • Following entry is found in the stdout.log :

    # A fatal error has been detected by the SAP Java Virtual Machine:
    #
    # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000011648c0, pid=4772, tid=10480
    # faulting address (tried to read): 0x00000000072c4000
    #
    # JRE version: 6.0_37-b06
    # Java VM: SAP Java Server VM (6.1.044 21.1-b06 Oct 31 2012 10:44:56 - 61_REL - optU - windows amd64 - 6 - bas2:182728 (mixed mode) compressed oops)
    # Problematic frame:
    # C  [zip.dll+0x48c0]  Java_java_util_zip_ZipEntry_initFields+0x1e5c (sp=0x000000001e86eb60) (pc=0x00000000011648c0)
    #
  • hs_err_pidXXXX.log is generated in Tomcat directory which has further details of the crash and the following error was observed from Linux Environment:
    # Java VM: SAP Java Server VM (6.1.058 24.45-b08 Nov  4 2013 00:32:19 - 61_REL - optU - linux amd64 - 6 - bas2:205339 (mixed mode) compressed oops)
    # Problematic frame:
    # C  [libzip.so+0x7131]  Java_zip_deflate_slow+0x51 (sp=0x00002b0282375460) (pc=0x00002b025f364131)
  • The Tomcat glf trace logs also show errors as well

               Error on calling destroy on a not null IContext: CoreException - cause>>>com.businessobjects.sdk.core.CoreException<<< 
                         com.businessobjects.sdk.core.CoreException
                          at com.businessobjects.sdk.core.internal.service.CoreContext.destroySharedData(CoreContext.java:217)
                          at com.businessobjects.sdk.core.internal.service.CoreContext.destroy(CoreContext.java:240)
                          at com.sap.webi.client.toolkit.LoginInfo.free(LoginInfo.java:357)
                          at com.sap.webi.client.toolkit.SessionContext.free(SessionContext.java:75)
                          at com.sap.webi.client.toolkit.SessionContext.logoff(SessionContext.java:113)
                          at com.sap.webi.client.toolkit.SessionContextManager.releaseSessionContext(SessionContextManager.java:56)
                          at com.sap.webi.client.toolkit.SessionContextManager.releaseSessionContext(SessionContextManager.java:154)
                          at com.businessobjects.adv_ivcdzview.CleanupWebSession.destroySessionContext(Unknown Source)
                          at com.businessobjects.adv_ivcdzview.CleanupWebSession.dispose(Unknown Source)
                          at com.businessobjects.webutil.clientaction.SessionCleanupListener$DisposalEntry.disposeIfNeeded(SessionCleanupListener.java:123)
                          at com.businessobjects.webutil.clientaction.SessionCleanupListener.sessionDestroyed(SessionCleanupListener.java:69)
                          at com.businessobjects.http.servlet.internal.ListenerRegistrationManager.sessionDestroyed(ListenerRegistrationManager.java:110)
                          at com.businessobjects.http.servlet.internal.BundlePathAwareServiceHandler.sessionDestroyed(BundlePathAwareServiceHandler.java:410)
                          at com.businessobjects.http.servlet.internal.ProxyServlet.sessionDestroyed(ProxyServlet.java:588)
                          at com.businessobjects.servletbridge.listener.ProxyApplicationLifeCycleListener.sessionDestroyed(ProxyApplicationLifeCycleListener.java:38)
                          at org.apache.catalina.session.StandardSession.expire(StandardSession.java:720)
                          at org.apache.catalina.ha.session.DeltaSession.expire(DeltaSession.java:435)
                          at org.apache.catalina.ha.session.DeltaSession.expire(DeltaSession.java:413)
                          at org.apache.catalina.ha.session.DeltaSession.isValid(DeltaSession.java:377)
                          at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:714)
                          at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:699)
                          at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1368)
                          at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1653)
                          at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1662)
                          at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1662)
                          at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1642)
                          at java.lang.Thread.run(Thread.java:662)


Read more...

Environment

  • Windows
  • Linux
  • Tomcat 6.x
  • Tomcat 7.x
  • Oracle JVM 1.6.x
  • SAP JVM 1.6.x
  • SAP BusinessObjects Business Intelligence Platform BI 4.x

Product

SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.1

Keywords

zip.dll+0x48c0, Java_java_util_zip, reading, address, crash, compression , KBA , emkba , bidep , 4.1 , 4.0 , 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.