Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Detect illegal concurrent usage of LogicalConnectionManagedImpl

Description

Apparently some applications or containers have integration code which could attempt to release the resources managed by a LogicalConnectionManagedImpl concurrently.
While this is IMO a bug in either the integration code or the user's code, it triggers an NPE in ORM which makes it a bit obscure. We can avoid the NPE with slightly more defensive code, which I plan to introduce with this patch.

I still plan to throw an exception, just possibly hinting about the real cause.

Activity

Show:

Sanne GrinoveroAugust 10, 2020 at 2:02 PM

Hi Scott, there’s one LogicalConnectionManagedImpl for each Session - with the exception of shared sessions, when they share a connection they will share the same logical connection manager.

SessionFactory doesn’t have a reference to these.

Scott MarlowAugust 10, 2020 at 1:42 PM
Edited

Does the SessionFactory have access to the LogicalConnectionManagedImpl or only the Session?

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created August 10, 2020 at 8:35 AM
Updated August 10, 2020 at 3:41 PM
Resolved August 10, 2020 at 9:58 AM