RE: [eclipselink-users] connection management

[James Sutherland <jamesssss@xxxxxxxxx>]

I suppose you could set your min connections to 0, that way no connections
will be used when not in use.  You could also implement your own DataSource
to meet your unique requirements.

You could also close your EntityManagerFactory when not in use, or logout
from your ServerSession.



vrmerlin wrote:
> 
> 
> We don't have a central application server where we can pool connections.
> The architecture is about 1,500 different processes running on many
> different machines - it's a control system that connects over 60,000
> different devices. Each process would have a connection to the database,
> and
> utilize JPA objects to load configuration data. So, I want each process to
> drop its connection if not being used. Is that still a JTA datasource
> solution? Is there a link you can refer me to on how to do this?
> 
> As for supercomputing, we're usually #1 -- hopefully again soon. :-)
> 
> John
> 
> 
> -----Original Message-----
> From: eclipselink-users-bounces@xxxxxxxxxxx
> [mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of Michael
> O'Brien
> Sent: Wednesday, October 29, 2008 7:03 AM
> To: EclipseLink User Discussions
> Subject: RE: [eclipselink-users] connection management
> 
> John,
> 	Right, You should be ok using a standard JTA datasource that is
> setup for pooling on your application server as long as you don't timeout
> in
> mid-transaction.
> 
> 	As an aside, I find it very interesting to help out a group in close
> proximity to the #2 supercomputer in the world at your lab - just under
> the
> other new June 2008 Roadrunner IBM system for the DOE built with IBM
> PlayStation cell processor blades.  If we can help get your 500 teraflop
> speed above the new June 2008 1 petaflop maximum it would be very good.
> 
> 	thank you
> 	/michael  
> 
> -----Original Message-----
> From: Tim Hollosy [mailto:hollosyt@xxxxxxxxx]
> Sent: Tuesday, October 28, 2008 20:16
> To: EclipseLink User Discussions
> Subject: Re: [eclipselink-users] connection management
> 
> 
> Sounds like a connection pool? No?
> 
> ./tch
> 
> 
> 
> On Tue, Oct 28, 2008 at 6:17 PM, John Fisher <fisher23@xxxxxxxx> wrote:
>>
>>
>> Hi folks,
>>
>>
>>
>> We are looking at using EclipseLink/JPA for a large distributed
> environment
>> (1,500+ processes). Many of the processes will need to get to the
>> database
>> (Oracle), but not that frequently. So. is there a way to have EclipseLink
>> "give up" its connections, after a timeout period, then automatically
>> reestablish them as needed?
>>
>>
>>
>> Thanks,
>> John
> 


-----
---
http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland 
http://www.eclipse.org/eclipselink/
 EclipseLink ,  http://www.oracle.com/technology/products/ias/toplink/
TopLink 
Wiki:  http://wiki.eclipse.org/EclipseLink EclipseLink , 
http://wiki.oracle.com/page/TopLink TopLink 
Forums:  http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink , 
http://www.nabble.com/EclipseLink-f26430.html EclipseLink 
Book:  http://en.wikibooks.org/wiki/Java_Persistence Java Persistence 
-- 
View this message in context: http://www.nabble.com/connection-management-tp20217228p20246313.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.