SAP Knowledge Base Article - Preview

3456966 - Traffic Control violation Error after update to SAP JVM 8.1.097

Symptom

"500 internal server error" or "No more memory for FCA" "Traffic Control peer timeout" on NWA, after updating the SAP JVM.

Dev_icm

[Thr 140199866119936] *** WARNING => IcmReadFromConn(id=57/21394): temporarily out of MPI buffers -> roll out [icxxthrio.c  3427]
and
[Thr 140199865591552] *** ERROR => HttpJ2EETriggerServer: alloc failed: out of MPI blocks [http_j2ee2.c 1645]

After triggering thread dumps during application hanging situation, in std_serverX.out, the following similar stacktrace can be seen:

java.lang.Thread.State: BLOCKED (on object monitor)
    at iaik.security.ssl.SSLTransport.a(ZZ)V(SourceFile:715)
    - waiting to lock <0x000000073abd3518> (a iaik.security.ssl.SSLTransport)
    at iaik.security.ssl.SSLTransport.shutdown()V(SourceFile:696)
    at iaik.security.ssl.SSLTransport.close()V(SourceFile:686)
    at iaik.security.ssl.SSLOutputStream.close()V(SourceFile:188)
    - locked <0x000000073abd36c0> (a iaik.security.ssl.ag)
    at java.io.FilterOutputStream.close()V(FilterOutputStream.java:159)
    at com.sun.jndi.ldap.Connection.flushAndCloseOutputStream()V(Connection.java:704)
    at com.sun.jndi.ldap.Connection.cleanup([Ljavax/naming/ldap/Control;Z)V(Connection.java:666)
    - locked <0x000000073af3f520> (a com.sun.jndi.ldap.Connection)
    at com.sun.jndi.ldap.LdapClient.close([Ljavax/naming/ldap/Control;Z)V(LdapClient.java:446)
    - locked <0x000000073af3f720> (a com.sun.jndi.ldap.LdapClient)
    at com.sun.jndi.ldap.LdapCtx.closeConnection(Z)V(LdapCtx.java:2960)
    at com.sun.jndi.ldap.LdapCtx.close()V(LdapCtx.java:2670)
    - locked <0x000000073af42190> (a com.sun.jndi.ldap.LdapCtx)

and

java.lang.Thread.State: BLOCKED (on object monitor)
    at iaik.security.ssl.ag.a(II)V(SourceFile:459)
    - waiting to lock <0x000000073abd36c0> (a iaik.security.ssl.ag)
    at iaik.security.ssl.SSLTransport.a(ZZ)V(SourceFile:733)
    - locked <0x000000073abd3518> (a iaik.security.ssl.SSLTransport)
    at iaik.security.ssl.ai.a()Z(SourceFile:333)
    at iaik.security.ssl.ai.read([BII)I(SourceFile:147)
    - locked <0x000000073abd3740> (a iaik.security.ssl.ab)
    at java.io.BufferedInputStream.fill()V(BufferedInputStream.java:246)
    at java.io.BufferedInputStream.read1([BII)I(BufferedInputStream.java:286)
    at java.io.BufferedInputStream.read([BII)I(BufferedInputStream.java:345)
    - locked <0x000000073af3f6f8> (a java.io.BufferedInputStream)
    at com.sun.jndi.ldap.Connection.run()V(Connection.java:906)
    at java.lang.Thread.run()V(Thread.java:838)


Read more...

Environment

  • SAP NetWeaver Application Server for Java
  • SAP JAVA Virtual Machine 8.1 as of patch level 97 up to 100.

Product

SAP NetWeaver 7.5

Keywords

SocketTimeoutErrors, Deadlock , IAIK, SAP JVM 8.1.098,SAP JVM 8.1.097,com.sun.jndi.ldap.LdapCtx.closeConnection,com.sun.jndi.ldap.Connection.flushAndCloseOutputStream , KBA , BC-JAS-SEC-CPG , Cryptography , BC-JVM , SAP Java Virtual Machine , SV-PERF-JAS , SAP NetWeaver AS Java related performance issues , 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.