When using MS SQL driver, stuck threads on waiting for Jdbc Connection cause bad performance (Doc ID 1387931.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle WebLogic Server - Version 10.3 to 10.3.6
Information in this document applies to any platform.

Symptoms

Weblogic Server configured with MS SQL driver for Data Source settings shows bad performance under high load.

ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE native
jrockit.net.SocketNativeIO.readBytesPinned(Native Method)
jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:32)
java.net.SocketInputStream.socketRead0(SocketInputStream.java)
java.net.SocketInputStream.read(SocketInputStream.java:129)
weblogic.jdbc.sqlserver.SQLServerByteOrderedDataReader.makeMoreDataAvailable(Unknown Source) weblogic.jdbc.sqlserver.SQLServerByteOrderedDataReader.receive(Unknown Source)
weblogic.jdbc.sqlserver.tds.TDSRPCRequest.submitRequest(Unknown Source)
weblogic.jdbc.sqlserver.tds.TDSRPCNonCursorExecuteRequest.submitExecute(Unknown Source)
weblogic.jdbc.sqlserver.tds.TDSRPCExecuteRequest.execute(Unknown Source)
weblogic.jdbc.sqlserver.SQLServerImplStatement.execute(Unknown Source)
weblogic.jdbc.base.BaseStatement.commonExecute(Unknown Source)
weblogic.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
weblogic.jdbc.base.BasePreparedStatement.executeQuery(Unknown Source)
weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:128)
com.systemware.common.jdbc.pm.MonitoredPreparedStatement.executeQuery(Unknown Source)
com.systemware.xri.engine.FlatTopicEngine.findTopicInstances(Unknown Source)
com.systemware.xri.engine.FlatTopicEngine.readTopicInstance(Unknown Source)
com.systemware.xri.engine.FlatTopicEngine.readTopicInstance(Unknown Source)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms