[hibernate-dev] Upgrading Hibernate Causes null index column for collection error for List

We are trying to upgrade hibernate from version 4.3.5 to 5.4.0. With this the jpa version also changes from hibernate-jpa-2.1 to jpa-2.2. After the upgrade we get the following error when using the List<> collection with @OrderColumn "javax.persistence.PersistenceException: org.hibernate.Hibernate

Re: [hibernate-dev] Does hibernate multi-tenancy lead to reduced heap usage

Including the dev mailing group to get a few suggestions on my question. Thanks! On Wed, Sep 23, 2015 at 4:54 PM, amit shah wrote: > We are planning to integrate hibernate 4 multi-tenancy feature into our > application. With this feature I assume we would have only one session >

[hibernate-dev] Hibernate 4 Multi-tenancy Issue - No Entity Persisters Found

Hello, I have been trying to integrate hibernate 4 multi-tenancy support in our application but I get the below exception on executing an hql query java.lang.ArrayIndexOutOfBoundsException: 0 at org.hibernate.jpa.spi.AbstractEntityManagerImpl.resultClassChecking(AbstractEntityManagerImpl.jav

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

ema 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 >> <https://hibernate.atlassian.net/browse/HHH-9740>on jira but to get a >> quick response I posted the issue here again. >> I do

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

rnate* (not your code) trying to > open a connection, then that would be a bug. If that is the case, please > open a Jira, and be sure to include (a) a test case and (b) the full stack > trace for the NPE. > On Apr 22, 2015 7:07 AM, "amit shah" wrote: > >> I'm u

[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] Performance issue blocking upgrade to hibernate 4.3.5

, I'll be very happy to look into it and get it > fixed. > > -- Sanne > > On 22 September 2014 05:56, amit shah wrote: > > Hello, > > > > We have been blocked by a performance degradation issue logged as > HHH-9396 > > <https://hibernate.atlassian.net/

[hibernate-dev] Performance issue blocking upgrade to hibernate 4.3.5

Hello, We have been blocked by a performance degradation issue logged as HHH-9396 . Since there has been no response on jira, I would like to ask on this dev forum on the further plan. Kindly have a look and respond. Thanks, Amit.

Re: [hibernate-dev] Session.evict does not allow nulls after upgrade

ons about the development of Hibernate, not for > usage discussions. > > The behavior you describe sounds the most reasonable to me actually, tbh. > Also, generic code can (should, I'd argue) still do null checks... > > > On Thu, May 8, 2014 at 6:51 AM, amit shah wrote: &g

[hibernate-dev] Session.evict does not allow nulls after upgrade

We upgraded hibernate from 3.6.0 to 4.3.5 but the application fails if null is passed to Session.evict() The application passes null since the code is generic. Are there any alternatives? Thanks, Amit. ___ hibernate-dev mailing list hibernate-dev@lists.