Symptom
- While polling data from IBM DB2 using JMS adapter, the interfaces are stuck.
- Despite restarting the system, the issue continues to persist.
- The Database size continues to grow.
- Thread dumps shows the below logs:
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Ljava/io/FileDescriptor;[BIII)I(Native Method)
at java.net.SocketInputStream.socketRead(Ljava/io/FileDescriptor;[BIII)I(SocketInputStream.java:116)
at java.net.SocketInputStream.read([BIII)I(SocketInputStream.java:171)
- additional info (remote: eu04qgd0-vir/10.128.185.62:5912, local: localhost/127.0.0.1:33795)
at java.net.SocketInputStream.read([BII)I(SocketInputStream.java:141)
- additional info (remote: eu04qgd0-vir/10.128.185.62:5912, local: localhost/127.0.0.1:33795)
at com.ibm.db2.jcc.t4.y.b(I)I(y.java:230)
at com.ibm.db2.jcc.t4.y.c(I)I(y.java:342)
at com.ibm.db2.jcc.t4.y.c()V(y.java:455)
at com.ibm.db2.jcc.t4.y.v()V(y.java:1230)
at com.ibm.db2.jcc.t4.ab.h(Lcom/ibm/db2/jcc/am/li;)V(ab.java:167)
at com.ibm.db2.jcc.t4.p.g(Lcom/ibm/db2/jcc/am/li;)V(p.java:93)
at com.ibm.db2.jcc.t4.b.readSetClientInfo_(Lcom/ibm/db2/jcc/am/ei;)V(b.java:3292)
at com.ibm.db2.jcc.am.ei.b(Lcom/ibm/db2/jcc/am/lc;)V(ei.java:73)
at com.ibm.db2.jcc.am.en.b(Lcom/ibm/db2/jcc/am/lc;)V(en.java:196)
Read more...
Environment
- SAP NetWeaver Process Integration
- SAP NetWeaver Process Orchestration
Product
Keywords
IBM DB2, database growth, JMS adapter, Message polling, com.ibm.db2.jcc.t4.y.b. , KBA , BC-XI-CON-JMS , JMS Adapter , 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.