[hibernate-dev] Multitenancy Per Schema Fails With NPE

I'm using schema based multi-tenancy providing implementations for both MultiTenantConnectionProvider & CurrentTenantIdentifierResolver. Trying to get a hibernate session for a single tenant fails with an NPE. Looking into the source code, it seems that JDBCServicesImpl initializes the connectionP

Re: [hibernate-dev] Multitenancy Per Schema Fails With NPE

1) This is a list for discussing the development of Hibernate itself, not for discussing usage of Hibernate. Please use the forums, StackOverflow, or #hibernate IRC for user questions. 2) If this really leads to a NPE in *Hibernate* (not your code) trying to open a connection, then that would be

Re: [hibernate-dev] Multitenancy Per Schema Fails With NPE

I did log a blocker issue on jira but to get a quick response I posted the issue here again. I do not see any traction on the jira issue, neither did stackoverflow or the IRC chat help out. Any help would be appreciated. Thanks ! On Wed, Apr 22, 20

Re: [hibernate-dev] Multitenancy Per Schema Fails With NPE

You are trying to use auto schema validation. That is not yet supported for multi-tenancy. None of the auto schema tools are. If you need to run any of the schema tools, you will need to do so manually. On Mon, Apr 27, 2015 at 12:35 AM, amit shah wrote: > I did log a blocker issue >

Re: [hibernate-dev] Multitenancy Per Schema Fails With NPE

Great! that helped. Removing the config property worked out. On Mon, Apr 27, 2015 at 4:29 PM, Steve Ebersole wrote: > You are trying to use auto schema validation. That is not yet supported > for multi-tenancy. None of the auto schema tools are. If you need to run > any of the schema tools, y