Jump to: navigation, search

Configuring Database Sessions (ELUG)

Revision as of 14:09, 16 July 2012 by Rick.sapir.oracle.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Elug draft icon.png For the latest EclipseLink documentation, please see http://www.eclipse.org/eclipselink/documentation/



This table lists the configurable options for database sessions.


Option Workbench
Java

Configuring External Connection Pools

Supported

Supported

Configuring a Primary Mapping Project

Supported

Supported

Configuring a Session Login

Supported

Supported

Configuring Logging

Supported

Supported

Configuring Multiple Mapping Projects

Supported

Supported

Configuring a Performance Profiler

Supported

Supported

Configuring an Exception Handler

Supported

Supported

Configuring a Session Customizer Class

Supported

Supported

Configuring the Server Platform

Supported

Supported

Configuring Session Event Listeners

Supported

Supported

Configuring a Coordinated Cache

Supported

Supported

Configuring the Integrity Checker

Supported

Supported

Configuring Named Queries at the Session Level

Unsupported

Supported


Configuring External Connection Pools

Unlike a server session, a database session does not provide internal connection pools. A database session only has a single database connection that it uses for its life cycle.

We recommend that you use a server and client session in a three-tier environment. Alternatively, you can use a database session with an external connection pool (see Configuring External Connection Pooling): in this case, you should allocate a new database session per user/thread or request.

WARNING: Do not allow the concurrent use of a database session by multiple users/threads.


The usage of an external connection pool reduces the number of the database session login and logout attempts to acquire the database connection.




Copyright Statement