[Hibernate-JIRA] Created: (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
2:37 p.m.
NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode
manually
-------------------------------------------------------------------------------------------------
Key: HHH-7305
URL: https://hibernate.onjira.com/browse/HHH-7305
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 4.1.3
Environment: cfg.setProperty(Environment.MULTI_TENANT,
MultiTenancyStrategy.DATABASE.name());
Reporter: Christian kalkhoff
Priority: Critical
When multi tenancy is used and hibernate.connection.release_mode is not set, one gets a
NPE in LogicalConnectionImpl because it accesses a (non-multi-tenancy)connection provider
to determine the release mode.
Stack trace:
java.lang.NullPointerException
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.determineConnectionReleaseMode(LogicalConnectionImpl.java:119)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:100)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:82)
at
org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.<init>(JdbcCoordinatorImpl.java:75)
at
org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.<init>(TransactionCoordinatorImpl.java:87)
at org.hibernate.internal.SessionImpl.<init>(SessionImpl.java:249)
at
org.hibernate.internal.SessionFactoryImpl$SessionBuilderImpl.openSession(SessionFactoryImpl.java:1835)
...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:38 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
[
https://hibernate.onjira.com/browse/HHH-7305?page=com.atlassian.jira.plug...
]
Christian kalkhoff commented on HHH-7305:
-----------------------------------------
I also had to extend JtaSessionContext and override protected ConnectionReleaseMode
getConnectionReleaseMode() to return return ConnectionReleaseMode.AFTER_TRANSACTION; to
work around this bug.
NPE in LogicalConnectionImpl when multi tenancy is used without
providing a release mode manually
-------------------------------------------------------------------------------------------------
Key: HHH-7305
URL: https://hibernate.onjira.com/browse/HHH-7305
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 4.1.3
Environment: cfg.setProperty(Environment.MULTI_TENANT,
MultiTenancyStrategy.DATABASE.name());
Reporter: Christian kalkhoff
Priority: Critical
When multi tenancy is used and hibernate.connection.release_mode is not set, one gets a
NPE in LogicalConnectionImpl because it accesses a (non-multi-tenancy)connection provider
to determine the release mode.
Stack trace:
java.lang.NullPointerException
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.determineConnectionReleaseMode(LogicalConnectionImpl.java:119)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:100)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:82)
at
org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.<init>(JdbcCoordinatorImpl.java:75)
at
org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.<init>(TransactionCoordinatorImpl.java:87)
at org.hibernate.internal.SessionImpl.<init>(SessionImpl.java:249)
at
org.hibernate.internal.SessionFactoryImpl$SessionBuilderImpl.openSession(SessionFactoryImpl.java:1835)
...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:47 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
[
https://hibernate.onjira.com/browse/HHH-7305?page=com.atlassian.jira.plug...
]
Jegan commented on HHH-7305:
----------------------------
I am facing the same issue. It is a critical issue as we are not able to upgrade Hibernate
to 4.1.2 to use Multi Tenancy support.
NPE in LogicalConnectionImpl when multi tenancy is used without
providing a release mode manually
-------------------------------------------------------------------------------------------------
Key: HHH-7305
URL: https://hibernate.onjira.com/browse/HHH-7305
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 4.1.3
Environment: cfg.setProperty(Environment.MULTI_TENANT,
MultiTenancyStrategy.DATABASE.name());
Reporter: Christian kalkhoff
Priority: Critical
When multi tenancy is used and hibernate.connection.release_mode is not set, one gets a
NPE in LogicalConnectionImpl because it accesses a (non-multi-tenancy)connection provider
to determine the release mode.
Stack trace:
java.lang.NullPointerException
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.determineConnectionReleaseMode(LogicalConnectionImpl.java:119)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:100)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:82)
at
org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.<init>(JdbcCoordinatorImpl.java:75)
at
org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.<init>(TransactionCoordinatorImpl.java:87)
at org.hibernate.internal.SessionImpl.<init>(SessionImpl.java:249)
at
org.hibernate.internal.SessionFactoryImpl$SessionBuilderImpl.openSession(SessionFactoryImpl.java:1835)
...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:51 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
[
https://hibernate.onjira.com/browse/HHH-7305?page=com.atlassian.jira.plug...
]
Christian kalkhoff commented on HHH-7305:
-----------------------------------------
As it turns out, my work around does not really work in JTA environments. :-(
NPE in LogicalConnectionImpl when multi tenancy is used without
providing a release mode manually
-------------------------------------------------------------------------------------------------
Key: HHH-7305
URL: https://hibernate.onjira.com/browse/HHH-7305
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 4.1.3
Environment: cfg.setProperty(Environment.MULTI_TENANT,
MultiTenancyStrategy.DATABASE.name());
Reporter: Christian kalkhoff
Priority: Critical
When multi tenancy is used and hibernate.connection.release_mode is not set, one gets a
NPE in LogicalConnectionImpl because it accesses a (non-multi-tenancy)connection provider
to determine the release mode.
Stack trace:
java.lang.NullPointerException
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.determineConnectionReleaseMode(LogicalConnectionImpl.java:119)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:100)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:82)
at
org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.<init>(JdbcCoordinatorImpl.java:75)
at
org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.<init>(TransactionCoordinatorImpl.java:87)
at org.hibernate.internal.SessionImpl.<init>(SessionImpl.java:249)
at
org.hibernate.internal.SessionFactoryImpl$SessionBuilderImpl.openSession(SessionFactoryImpl.java:1835)
...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:47 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
[
https://hibernate.onjira.com/browse/HHH-7305?page=com.atlassian.jira.plug...
]
Jegan updated HHH-7305:
-----------------------
Attachment: SchemaBasedMultiTenancyTest.java
JUnit to reproduce the NullPointerException in SettingsFactory.buildSettings()
NPE in LogicalConnectionImpl when multi tenancy is used without
providing a release mode manually
-------------------------------------------------------------------------------------------------
Key: HHH-7305
URL: https://hibernate.onjira.com/browse/HHH-7305
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 4.1.3
Environment: cfg.setProperty(Environment.MULTI_TENANT,
MultiTenancyStrategy.DATABASE.name());
Reporter: Christian kalkhoff
Priority: Critical
Attachments: SchemaBasedMultiTenancyTest.java
When multi tenancy is used and hibernate.connection.release_mode is not set, one gets a
NPE in LogicalConnectionImpl because it accesses a (non-multi-tenancy)connection provider
to determine the release mode.
Stack trace:
java.lang.NullPointerException
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.determineConnectionReleaseMode(LogicalConnectionImpl.java:119)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:100)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:82)
at
org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.<init>(JdbcCoordinatorImpl.java:75)
at
org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.<init>(TransactionCoordinatorImpl.java:87)
at org.hibernate.internal.SessionImpl.<init>(SessionImpl.java:249)
at
org.hibernate.internal.SessionFactoryImpl$SessionBuilderImpl.openSession(SessionFactoryImpl.java:1835)
...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:55 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
[
https://hibernate.onjira.com/browse/HHH-7305?page=com.atlassian.jira.plug...
]
Jegan commented on HHH-7305:
----------------------------
I have added a JUnit to reproduce this issue. It is the same JUnit from Hibernate, the
only difference is the line number 91 where I have explicitly set the connection release
mode to "after_statement". Running this test causes a NPE at
SettingsFactory.buildSettings method. I think, NPE in LogicalConnectionImpl comes in a JTA
environment if you do not specify a connection release mode.
The basic issue is that, connectionProvider in JdbcServices could be null in a Multi
tenant env. The fix could be to add supportsAggressiveRelease() method in
JdbcConnectionAccess class and access it from all places instead of accessing it from
ConnectionProvider. But, this may not be a right place for this method.
NPE in LogicalConnectionImpl when multi tenancy is used without
providing a release mode manually
-------------------------------------------------------------------------------------------------
Key: HHH-7305
URL: https://hibernate.onjira.com/browse/HHH-7305
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 4.1.3
Environment: cfg.setProperty(Environment.MULTI_TENANT,
MultiTenancyStrategy.DATABASE.name());
Reporter: Christian kalkhoff
Priority: Critical
Attachments: SchemaBasedMultiTenancyTest.java
When multi tenancy is used and hibernate.connection.release_mode is not set, one gets a
NPE in LogicalConnectionImpl because it accesses a (non-multi-tenancy)connection provider
to determine the release mode.
Stack trace:
java.lang.NullPointerException
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.determineConnectionReleaseMode(LogicalConnectionImpl.java:119)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:100)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:82)
at
org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.<init>(JdbcCoordinatorImpl.java:75)
at
org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.<init>(TransactionCoordinatorImpl.java:87)
at org.hibernate.internal.SessionImpl.<init>(SessionImpl.java:249)
at
org.hibernate.internal.SessionFactoryImpl$SessionBuilderImpl.openSession(SessionFactoryImpl.java:1835)
...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:50 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
[
https://hibernate.onjira.com/browse/HHH-7305?page=com.atlassian.jira.plug...
]
Jegan commented on HHH-7305:
----------------------------
Is there any update on this critical issue? Is this going to be fixed soon? Without the
fix for this we may not be able to use the multi-tenancy feature.
NPE in LogicalConnectionImpl when multi tenancy is used without
providing a release mode manually
-------------------------------------------------------------------------------------------------
Key: HHH-7305
URL: https://hibernate.onjira.com/browse/HHH-7305
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 4.1.3
Environment: cfg.setProperty(Environment.MULTI_TENANT,
MultiTenancyStrategy.DATABASE.name());
Reporter: Christian kalkhoff
Priority: Critical
Attachments: SchemaBasedMultiTenancyTest.java
When multi tenancy is used and hibernate.connection.release_mode is not set, one gets a
NPE in LogicalConnectionImpl because it accesses a (non-multi-tenancy)connection provider
to determine the release mode.
Stack trace:
java.lang.NullPointerException
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.determineConnectionReleaseMode(LogicalConnectionImpl.java:119)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:100)
at
org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:82)
at
org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.<init>(JdbcCoordinatorImpl.java:75)
at
org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.<init>(TransactionCoordinatorImpl.java:87)
at org.hibernate.internal.SessionImpl.<init>(SessionImpl.java:249)
at
org.hibernate.internal.SessionFactoryImpl$SessionBuilderImpl.openSession(SessionFactoryImpl.java:1835)
...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:41 p.m.
New subject: [Hibernate-JIRA] (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
9:43 p.m.
New subject: [Hibernate-JIRA] (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
11:11 p.m.
New subject: [Hibernate-JIRA] (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
11:13 p.m.
New subject: [Hibernate-JIRA] (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
10:28 a.m.
New subject: [Hibernate-JIRA] (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
2:03 p.m.
New subject: [Hibernate-JIRA] (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually
4523
days inactive
4615
days old
hibernate-issues@lists.jboss.org
12 comments
4 participants
participants (4)
-
Christian kalkhoff (JIRA) -
Jegan (JIRA)
-
Steve Ebersole (JIRA)
-
Strong Liu (JIRA)