After upgrading to WebLogic Server 12.2.1.4, Certain Functions that Read CLOB Data Throw: "java.sql.SQLException: Connection has already been closed" error (Doc ID 2693946.1)

Last updated on AUGUST 29, 2023

Applies to:

Oracle WebLogic Server - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Goal

After upgrading to Weblogic 12.2.1.4, certain functions (for example length() and getCharacterStream()) that read CLOB data are throwing java.sql.SQLException: Connection has already been closed errors.

Stack Trace that is seen:

Disabling "Wrap Data Types" for the datasource fixes the error, but what has changed after upgrading the application from WLS 12.2.1.2 to WLS 12.2.1.4?

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

After upgrading to WebLogic Server 12.2.1.4, Certain Functions that Read CLOB Data Throw: "java.sql.SQLException: Connection has already been closed" error (Doc ID 2693946.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

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