| Eclipselink Connection Pool Usage [message #1723037] |
Thu, 11 February 2016 08:28  |
 Havard Kristiansen
Messages: 3
Registered: November 2015 |
Junior Member |
|
|
I am attempting to create a JSF application running on WebLogic 12cR2, and I need to run a user specific database procedure call before any database operations can be executed.
Ideally, we would like to grab and keep one connection until the request is completed, so we only have to execute the database call once.
In the current version, EclipseLink grabs a connection from the pool for every fetch. Eclipselink has no clue of transactions in the current version, as we use JTA. We can minimize the number of fetches tuning each query, but as the application grows more complex, we would really like to have control over connection pool usage.
We are unsure how to go about this, and have tried a number of things; Open Session in View filter with UserTransaction, @PersistenceContext, CDI injection of @RequestScoped EntityManager, @Stateless EJB-beans, exclusive connections, but all to no avail. It is probably something fundamental we do not understand about JTA/Eclipselink.
I have included a small(ish) sample JSF-application to show the problem. It will run on a Weblogic 12CR1/R2 with a data source with jndi-name "jdbc.plainDS" against HR-schema with Employees/Departments table in an Oracle database. If you debug, you will see it grabs a connection when it fetches Employees for each Department.
We do not know how to go about minimizing connection pool usage.
Is JTA the way to go?
Isn't this a common requirement when using VPD?
Is connection pool a bad choice for this requirement?
How can we achieve minimal connection pool usage?
I do not know if Eclipselink forum is the right place for this question, but at this time, any suggestions or nudges in the right direction will be greatly appreciated!
Regards,
Håvard
|
|
|
| Re: Eclipselink Connection Pool Usage [message #1723099 is a reply to message #1723037] |
Thu, 11 February 2016 15:24  |
Chris Delahunt
Messages: 1389
Registered: July 2009 |
Senior Member |
|
|
EclipseLink tries to be more efficient when configured to use a default read pool by releasing connections immediatley after a query is done so that fewer read connections can be shared among more threads. The code within a transaction operates the same.
What it seems like you want is to have the session underlying your context hold onto a single connection for its life, and only release it when it is closed. This is refered to as exclusive connection mode and can be configured as described here
EclipseLink also has additional VPD support described here
[Updated on: Thu, 11 February 2016 15:26] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.02397 seconds
] 
Search
Help
Register
Login
Home
