How can the connection which is still associated with a valid
transaction be categorised as a leaked connection?I also expect the same
behavior expected by Noah.
Thanks,
Sahoo
On Saturday 29 June 2013 03:00 AM, Marina Vatkina wrote:
> I don't think the resource manager or transaction manager stop the
> clocks when transaction is suspended.
>
> -marina
>
> On 6/28/13 2:20 PM, Noah White wrote:
>> If an EJB method with a TX attribute of REQUIRES_NEW is invoked and
>> it in turn invokes an EJB method with a TX attribute of NOT_SUPPORTED
>> the container is supposed to suspend the association of the tx
>> context with the current thread before invoking the NOT_SUPPORTED
>> method.
>>
>> My question is if the NOT_SUPPORTED method takes longer then the JDBC
>> Connection Pool's "Connection Leak Timeout" will it get tripped or
>> does this timeout not apply while a TX context is suspended?
>>
>> I hope for the later but I suspect the former. Can anyone clarify.
>> This is with Glassfish 3.1.2.2, Oracle JDBC non-XA DataSource pool.
>>
>> Thanks,
>>
>> -Noah
>>
>