In before or after completion?
Also, it's not an expected behavior in an appserver. You need to release
connection after you finish using it (the container will make sure you
get the correctly associated connection every time you ask for it).
thanks,
-marina
Gordon Yorke wrote:
> TopLink acquires a connection for a transaction once a write to the database has been issued (update query, flush). Once the transaction commits the connection will be released.
> --Gordon
> -----Original Message-----
> From: Marina.Vatkina_at_Sun.COM [mailto:Marina.Vatkina_at_Sun.COM]On Behalf Of
> Marina Vatkina
> Sent: Wednesday, August 30, 2006 1:08 PM
> To: dev_at_glassfish.dev.java.net
> Cc: Kshitiz Saxena
> Subject: Re: EJB/ Toplink Query
>
>
> Hello Gordon,
>
> Does TopLink keep a connection for the duration of a transaction?
> If yes, when does it release such connection?
>
> thanks,
> -marina
>
> Gordon Yorke wrote:
>
>>Hello Sahoo,
>> When using Container Managed EntityManagers in GlassFish TopLink does not cache the connections. TopLink will only cache the connections when a Java SE style deployment is configured to connect to the datasource throught the direct connect properties in the persistence.xml file.
>>--Gordon
>>
>>-----Original Message-----
>>From: Sanjeeb.Sahoo_at_Sun.COM [mailto:Sanjeeb.Sahoo_at_Sun.COM]On Behalf Of
>>Sanjeeb Kumar Sahoo
>>Sent: Wednesday, August 30, 2006 6:06 AM
>>To: dev_at_glassfish.dev.java.net; Yorke Gordon J
>>Cc: Kshitiz Saxena
>>Subject: Re: EJB/ Toplink Query
>>
>>
>>Gordon,
>>
>>Can you please clarify the following: when TopLink Essential is used as
>>a JPA provider in GlassFish server environment, does it cache the
>>connections or not?
>>
>>Thanks,
>>Sahoo
>>Gordon Yorke wrote:
>>
>>
>>>Hello,
>>> When connected to a External Connection Pool TopLink Essentials
>>>will not cache the connections.
>>>--Gordon
>>>
>>> -----Original Message-----
>>> *From:* Jagadish.Ramu_at_Sun.COM [mailto:Jagadish.Ramu_at_Sun.COM]*On
>>> Behalf Of *Jagadish Prasath Ramu
>>> *Sent:* Saturday, August 19, 2006 6:16 AM
>>> *To:* dev_at_glassfish.dev.java.net
>>> *Cc:* Kshitiz Saxena
>>> *Subject:* EJB/ Toplink Query
>>>
>>> Hi,
>>> We are planning to implement a feature "connection-leak-tracing
>>> <http://www.glassfishwiki.org/gfwiki/attach/OnePagersOrFunctionalSpecs/ConnectionPoolOnePager.html>"
>>> for connection pool.
>>>
>>> This feature will help to diagnose potential connection leaks.
>>> (applications not returning connection to pool).
>>> "connection leak timeout" property : If a connection is not
>>> returned within "connection leak timeout", we report
>>> that the connection is leaked.
>>>
>>> I think, EJB/ toplink caches the connections. If it is caching the
>>> connections, connection-leak-tracing logic gets affected.
>>> Can someone please provide more background on this ?
>>>
>>> Thanks,
>>> -Jagadish/Kshitiz
>>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>