SAP Knowledge Base Article - Preview

1867475 - Server node out of memory caused by a thread processing Microsoft JDBC driver

Symptom

A thread used by Microsoft JDBC driver causes out of memory error on the server node. In the heap dump analysis, you have found out that the following thread takes big amount of memory:


"java.net.SocketInputStream.socketRead0(Ljava/io/FileDescriptor;[BIII)I(Native Method)
at java.net.SocketInputStream.read([BII)I (SocketInputStream.java:129)
at com.microsoft.sqlserver.jdbc.TDSChannel.read([BII)I(IOBuffer.java:1525)
at com.microsoft.sqlserver.jdbc.TDSReader.readPacket()ZIOBuffer.java:3317)
at com.microsoft.sqlserver.jdbc.TDSReader.nextPacket()Z(IOBuffer.java:3227)
at com.microsoft.sqlserver.jdbc.TDSReader.ensurePayload()Z(IOBuffer.java:3203)
at com.microsoft.sqlserver.jdbc.TDSReader.readBytes([BII)V(IOBuffer.java:3518)
at com.microsoft.sqlserver.jdbc.TDSReader.readWrappedBytes(I)[B(IOBuffer.java:3540)
at com.microsoft.sqlserver.jdbc.TDSReader.readUnsignedShort()I(IOBuffer.java:3456)
at com.microsoft.sqlserver.jdbc.ServerDTVImpl.getValuePrep(Lcom/microsoft/sqlserver/jdbc/TypeInfo;Lcom/microsoft/sqlserver/jdbc/TDSReader;)V(dtv.java:1888)"


Read more...

Environment

SAP Netweaver AS JAVA.

Product

SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5

Keywords

KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , 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.