Sorry, *was* only valid for JTA. As you mentioned we handle this
On Wed, Sep 21, 2016 at 8:29 AM Steve Ebersole <st...@hibernate.org> 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 <mihalcea.v...@gmail.com>
>> While reviewing and adding a test case for
>> I realized that if we enable the AvailableSettings.DISCARD_PC_ON_CLOSE
>> the database connection gets closed when the EntityManager is closed,
>> the EntityTransaction status remains ACTIVE.
>> I noticed that in the call:
>> But this method is no-op and deprecated as well.
>> Is this behavior intended? If the database connection was closed, at least
>> for RESOURCE_LOCAL, on most RDBMS engines, the underlying transaction gets
>> rolled back as well.
>> For JTA, the connection might still be open and allocated to the current
>> user since the TM controls when the resources are to be released.
>> Should we leave this behavior like that?
>> hibernate-dev mailing list
hibernate-dev mailing list