Troubleshooting J2CA Connection Pooling Issues in WebLogic Server Support Pattern (Doc ID 1135134.1)

Last updated on MAY 08, 2024

Applies to:

Oracle WebLogic Server - Version 6.1 to 8.1
Information in this document applies to any platform.

Purpose

Problem Description

J2CA (J2EE Connector Architecture) defines according to its specification "a standard architecture for connecting the Java 2 Platform, Enterprise Edition (J2EE) platform to heterogeneous EISs. Enterprise information systems provide the information infrastructure critical to the business processes of an enterprise. Examples of EISs include relational databases, enterprise resource planning (ERP) systems, mainframe transaction processing systems, and legacy database systems." As part of J2EE, WebLogic Server J2CA support (also referred to in the documentation as "Connector" or "Resource Adapter" support) "extends its system ... to support the connector architecture and is then assured of a seamless connectivity to multiple EISs."

This support pattern shows how the Connector Layer within WebLogic Server interacts with the deployed J2CA Adapter and WebLogic's Transaction Manager. It shows the use of debug properties to see the lifecycle of a pooled connection, of a local transaction, and of a distributed XA transaction. Information in this pattern is based on how J2CA is implemented in the WebLogic Server 8.1 release.

This document only considers the J2CA connector layer within WebLogic Server. The added value features for interoperability with external systems in Weblogic Integration are not considered here.

J2CA Troubleshooting

J2CA is an interoperability standard. Specific troubleshooting procedures depend on knowledge of both WebLogic Server, J2CA, and the Enterprise Information System (EIS) which is being accessed, and therefore are beyond the scope of a generic troubleshooting document. This pattern seeks instead to show a baseline behavior of the two areas of most complex interaction between WebLogic and the J2CA Adapter: connection handling and transaction handling. Deviations from this baseline can then be more easily spotted by both ad apter developers and application deployers.

This "baseline" is the use of the javasoft BlackBox Adapter with all deployment descriptors left at default values being accessed from an EJB in the WebLogic "jconnector" API example. See External Resources.