Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Configuring Database Sessions (ELUG)"
m (→Configuring External Connection Pools) |
m |
||
Line 1: | Line 1: | ||
+ | [[Image:Elug draft icon.png]] '''For the latest EclipseLink documentation, please see http://www.eclipse.org/eclipselink/documentation/ ''' | ||
+ | |||
+ | ---- | ||
+ | |||
+ | |||
<div style="float:right;border:1px solid #000000;padding:5px">__TOC__ | <div style="float:right;border:1px solid #000000;padding:5px">__TOC__ | ||
[[Special:Whatlinkshere/Configuring Database Sessions (ELUG)|Related Topics]]</div> | [[Special:Whatlinkshere/Configuring Database Sessions (ELUG)|Related Topics]]</div> |
Latest revision as of 15:09, 16 July 2012
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
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.