Check out this Jira issue that I integrated today:
https://hibernate.atlassian.net/browse/HHH-11120
If we enable this property, all the underlying resources are released right
away.
Otherwise (the default option), resources are released when the transaction
is ended (commit/rollback).
If this fi
I have no idea what "I could make use of it" means in this context. Make
use of what? That setting? That setting has zero effect today, unless I
missed something.
On Wed, Sep 21, 2016 at 8:33 AM Vlad Mihalcea
wrote:
> I could make use of it in a non-JTA environment. I guess we need to think
>
I could make use of it in a non-JTA environment. I guess we need to think
what should we do with the transaction status because now it's still
active, but if we try to rollback, we'll get an exception because the
connection was closed.
Vlad
On Wed, Sep 21, 2016 at 4:30 PM, Steve Ebersole wrote:
Sorry, *was* only valid for JTA. As you mentioned we handle this
differently today.
On Wed, Sep 21, 2016 at 8:29 AM Steve Ebersole wrote:
> DISCARD_PC_ON_CLOSE, as a concept, is only valid for JTA iirc.
>
> On Wed, Sep 21, 2016 at 8:11 AM Vlad Mihalcea
> wrote:
>
>> Hi,
>>
>> While reviewing
DISCARD_PC_ON_CLOSE, as a concept, is only valid for JTA iirc.
On Wed, Sep 21, 2016 at 8:11 AM Vlad Mihalcea
wrote:
> Hi,
>
> While reviewing and adding a test case for
> https://hibernate.atlassian.net/browse/HHH-11120,
> I realized that if we enable the AvailableSettings.DISCARD_PC_ON_CLOSE
>
