[Hibernate-JIRA] Created: (HHH-7190) [Performance] - Degradation hibernate time after migration hibernate 3.3.1.GA --> 4.0.1
by Lucas POUZAC (JIRA)
[Performance] - Degradation hibernate time after migration hibernate 3.3.1.GA --> 4.0.1
---------------------------------------------------------------------------------------
Key: HHH-7190
URL: https://hibernate.onjira.com/browse/HHH-7190
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 4.1.1, 4.0.1
Environment: java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
Reporter: Lucas POUZAC
Priority: Blocker
Attachments: hibernate.jpg
After migrating our application to version 4.0.1 of hibernate, we noticed a performance degradation. (same problem with the version 4.1.1)
Before migration, the average response time of our http request was 747ms (during load test).
Since the migration, the average response time is greater than 1200ms (during the same load test).
After recording the behavior of the JVM, we note that Hibernate uses methods of the java api with synchronized blocks (java.lang.reflect.Proxy.getProxyClass (...)). See attachment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[Hibernate-JIRA] Created: (HV-445) Ensure meta models are completely unmodifiable
by Gunnar Morling (JIRA)
Ensure meta models are completely unmodifiable
----------------------------------------------
Key: HV-445
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-445
Project: Hibernate Validator
Issue Type: Improvement
Reporter: Gunnar Morling
Fix For: 4.2.0.CR1
The internal meta model (BeanMetaDataImpl et al.) as well as the external one (BeanDescriptorImpl et al.) should be completely unmodifiable, as they could potentially be accessed from multiple threads at the same time.
I made some more fields final/unmodifiable with HV-371, but there are some places left which I couldn't change easily and need some more consideration:
* ConstraintDescriptorImpl#compositionType
* ElementDescriptorImpl#constraintDescriptors
* BeanMetaDatImpl#cascadedMembers (could be made unmodifiable after initialization instead of creating a new unmodifiable set with each call of getCascadedMembers()
When looking through the model I found it quite complex to find out which collection fields are already unmodifiable and which not. I therefore thought about introducing a marker annotation @Unmodifiable which could be used to document unmodifiable fields. WDYT?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[Hibernate-JIRA] Resolved: (HHH-1657) hql update generate wrong sql with joined subclass hierarcy
by Steve Ebersole (JIRA)
[ https://hibernate.onjira.com/browse/HHH-1657?page=com.atlassian.jira.plug... ]
Steve Ebersole resolved HHH-1657.
---------------------------------
Resolution: Fixed
Fix Version/s: 4.1.2
> hql update generate wrong sql with joined subclass hierarcy
> -----------------------------------------------------------
>
> Key: HHH-1657
> URL: https://hibernate.onjira.com/browse/HHH-1657
> Project: Hibernate ORM
> Issue Type: Bug
> Components: query-hql
> Environment: Hibernate 3.2.0cr1, Hibernate 3.1.3
> Reporter: Alexey Romanchuk
> Assignee: Steve Ebersole
> Fix For: 4.1.2
>
> Time Spent: 1h 2m
>
> Let suppose that we have two joined subclass entities: Parent (id PK) and Child (id PK) that mapped with joined subclass method.
> When I try to update Child by id with hql:
> update Child c set c.field = 'value' where c.id = 1234
> hibernate generates joined tables like
> insert into HT_parent select child0_.id as id from child child0_ inner join parent child0_1_ on child0_.id=child0_1_.id wher id in = 1234
> look at last condition. hibernate use id WITH OUT tables alias that cause sql exception: column reference "id" is ambiguous
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[Hibernate-JIRA] Updated: (HHH-1657) hql update generate wrong sql with joined subclass hierarcy
by Steve Ebersole (JIRA)
[ https://hibernate.onjira.com/browse/HHH-1657?page=com.atlassian.jira.plug... ]
Steve Ebersole updated HHH-1657:
--------------------------------
Assignee: Steve Ebersole (was: Gail Badner)
> hql update generate wrong sql with joined subclass hierarcy
> -----------------------------------------------------------
>
> Key: HHH-1657
> URL: https://hibernate.onjira.com/browse/HHH-1657
> Project: Hibernate ORM
> Issue Type: Bug
> Components: query-hql
> Environment: Hibernate 3.2.0cr1, Hibernate 3.1.3
> Reporter: Alexey Romanchuk
> Assignee: Steve Ebersole
>
> Let suppose that we have two joined subclass entities: Parent (id PK) and Child (id PK) that mapped with joined subclass method.
> When I try to update Child by id with hql:
> update Child c set c.field = 'value' where c.id = 1234
> hibernate generates joined tables like
> insert into HT_parent select child0_.id as id from child child0_ inner join parent child0_1_ on child0_.id=child0_1_.id wher id in = 1234
> look at last condition. hibernate use id WITH OUT tables alias that cause sql exception: column reference "id" is ambiguous
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[Hibernate-JIRA] Created: (HHH-7192) NullPointerException in QueryTranslatorImpl on erroneously typed delete query
by Alex Cruise (JIRA)
NullPointerException in QueryTranslatorImpl on erroneously typed delete query
-----------------------------------------------------------------------------
Key: HHH-7192
URL: https://hibernate.onjira.com/browse/HHH-7192
Project: Hibernate ORM
Issue Type: Bug
Components: query-hql
Affects Versions: 4.1.1, 4.1.0
Environment: Hibernate 4.1.1 (also affects 4.1.0), Postgresql
Reporter: Alex Cruise
Calling code:
val deleteFileQuery = "delete from FileInstanceEntity f where f.uri = 'file:/blah.txt'"
em.getTransaction.begin()
val q = em.createQuery(deleteFileQuery, classOf[FileInstanceEntity]) // FYI classOf[Foo] is the Scala equivalent of Java's Foo.class --
// and it's the presence of this parameter that causes problems
q.executeUpdate()
em.getTransaction.commit()
Stack trace:
Exception in thread "main" java.lang.NullPointerException
at org.hibernate.hql.internal.ast.QueryTranslatorImpl.getDynamicInstantiationResultType(QueryTranslatorImpl.java:571)
at org.hibernate.engine.query.spi.HQLQueryPlan.getDynamicInstantiationResultType(HQLQueryPlan.java:340)
at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:313)
at com.example.JpaEntityTest$.main(JpaEntityTest.scala:178)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years