August 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5494) Session is closed exception with some TX configurations

by Adam Warski (JIRA)

Session is closed exception with some TX configurations ------------------------------------------------------- Key: HHH-5494 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5494 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.5 Reporter: Adam Warski Assignee: Adam Warski See http://community.jboss.org/message/558450#558450 -- 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

15 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5493) java.lang.IllegalArgumentException: Parameter value [org.hibernate.ejb.criteria.expression.ParameterExpressionImpl@c000b6] was not matching type [java.lang.String]

by Lukas Jungmann (JIRA)

java.lang.IllegalArgumentException: Parameter value [org.hibernate.ejb.criteria.expression.ParameterExpressionImpl@c000b6] was not matching type [java.lang.String] ------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5493 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5493 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.5.2 Environment: JBossAS 6-M4 Reporter: Lukas Jungmann Attachments: app.zip -have attached simple JSF/JPA app for JBoss AS -deploy it on JBoss AS 6 M4 -load the app in a browser (/index.jsf) and click on the login button there => in the server log there is: Caused by: java.lang.IllegalArgumentException: Parameter value [org.hibernate.ejb.criteria.expression.ParameterExpressionImpl@c000b6] was not matching type [java.lang.String] at org.hibernate.ejb.AbstractQueryImpl.registerParameterBinding(AbstractQueryImpl.java:360) [:3.5.2-Final] at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:359) [:3.5.2-Final] at org.hibernate.ejb.criteria.CriteriaQueryCompiler$1$1.bind(CriteriaQueryCompiler.java:194) [:3.5.2-Final] at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:247) [:3.5.2-Final] at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:437) [:3.5.2-Final] at org.jboss.jpa.impl.tx.TransactionScopedEntityManager.createQuery(TransactionScopedEntityManager.java:276) [:2.0.0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_21] when I switch JPA provider from hibernate to eclipselink, app starts to behave correctly. I'm sorry if this is wrong place to report this issue. -- 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

15 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (BVAL-207) Hibernate 3.5.1-Final cannot parse order-by fragment

by Vladimir Kobetic (JIRA)

Hibernate 3.5.1-Final cannot parse order-by fragment ---------------------------------------------------- Key: BVAL-207 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-207 Project: Bean Validation Issue Type: Bug Environment: Hibernate 3.5.1-Final MySQL 5.0 Spring 2.5 Reporter: Vladimir Kobetic Priority: Critical When upgrading from Hibernate 3.2.5.ga to the newest Hibernate 3.5.1-Final with the newest build-with dependent libraries an error occurs during initial phase of launching application. I tried to build and run with all libraries from lib directory from Hibernate zip download. The order-by clause is configured in hbm.xml: <hibernate-mapping> <class name="com.test.Object" table="err"> <id name="id" type="java.lang.Long"> <generator class="native" /> </id> <set name="history" table="history" lazy="true" order-by="timestamp desc" cascade="all-delete-orphan"> <key column="object_id" /> <one-to-many class="com.test.Event" /> </set> </class> </hibernate-mapping> The exception is: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [applicationContext-dao-hibernate.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Unable to parse order-by fragment Caused by: org.hibernate.HibernateException: Unable to parse order-by fragment at org.hibernate.sql.ordering.antlr.OrderByFragmentTranslator.render(OrderByFragmentTranslator.java:66) at org.hibernate.sql.Template.renderOrderByStringTemplate(Template.java:310) at org.hibernate.persister.collection.AbstractCollectionPersister.<init>(AbstractCollectionPersister.java:557) at org.hibernate.persister.collection.OneToManyPersister.<init>(OneToManyPersister.java:84) at org.hibernate.persister.PersisterFactory.createCollectionPersister(PersisterFactory.java:104) and more... Caused by: java.lang.NullPointerException at org.hibernate.sql.ordering.antlr.OrderByFragmentParser.resolveFunction(OrderByFragmentParser.java:115) at org.hibernate.sql.ordering.antlr.GeneratedOrderByFragmentParser.expression(GeneratedOrderByFragmentParser.java:619) at org.hibernate.sql.ordering.antlr.GeneratedOrderByFragmentParser.sortKey(GeneratedOrderByFragmentParser.java:337) at org.hibernate.sql.ordering.antlr.GeneratedOrderByFragmentParser.sortSpecification(GeneratedOrderByFragmentParser.java:248) at org.hibernate.sql.ordering.antlr.GeneratedOrderByFragmentParser.orderByFragment(GeneratedOrderByFragmentParser.java:192) at org.hibernate.sql.ordering.antlr.OrderByFragmentTranslator.render(OrderByFragmentTranslator.java:60) ... 38 more -- 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

15 years, 7 months

7
15
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-576) IllegalArgumentException when trying to delete proxy class

by Tom (JIRA)

IllegalArgumentException when trying to delete proxy class ---------------------------------------------------------- Key: HSEARCH-576 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-576 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.1 Environment: Hibernate Search 3.2.1 Hibernate Core 3.5.2 Reporter: Tom -- 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

15 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5151) Update tutorial section of Hibernate Core to use Annotations

by Emmanuel Bernard (JIRA)

Update tutorial section of Hibernate Core to use Annotations ------------------------------------------------------------ Key: HHH-5151 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5151 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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

15 years, 8 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5451) deprecate cglib as bytecode provider

by Steve Ebersole (JIRA)

deprecate cglib as bytecode provider ------------------------------------ Key: HHH-5451 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5451 Project: Hibernate Core Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.0.Beta3 -- 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

15 years, 8 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-567) mvn release:prepare release:perform fails on branch builds

by Emmanuel Bernard (JIRA)

mvn release:prepare release:perform fails on branch builds ---------------------------------------------------------- Key: HSEARCH-567 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-567 Project: Hibernate Search Issue Type: Bug Reporter: Emmanuel Bernard I tried to release Hibernate 3.2.1 using the release plugin but the plugin failed putting the 3.2.0.final poms in the v_3_2_1 tag. -- 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

15 years, 8 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5438) Skip deployment of "irrelevant" modules

by Steve Ebersole (JIRA)

Skip deployment of "irrelevant" modules --------------------------------------- Key: HHH-5438 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5438 Project: Hibernate Core Issue Type: Improvement Components: build Affects Versions: 3.6.0.Beta2 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.0.Beta3 REF : http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip Specifically: * hibernate-testsuite * hibernate-jdbc3-testing * hibernate-jdbc4-testing Nice-to-haves, but which could be problematic * hibernate-distribution * hibernate (the root module) Really-really-really-nice-to-haves: * hibernate-documentation and all of its subs -- 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

15 years, 8 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5487) add <developers/> section to pom (else nexus complains on deploy)

by Steve Ebersole (JIRA)

add <developers/> section to pom (else nexus complains on deploy) ----------------------------------------------------------------- Key: HHH-5487 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5487 Project: Hibernate Core Issue Type: Task Components: build Affects Versions: 3.6.0.Beta2, 3.5.4 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.5, 3.6.0.Beta3 -- 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

15 years, 8 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-540) JTA transaction commit causes AssertionFailure: Access a Sealed WorkQueue which has not been sealed

by Tom Waterhouse (JIRA)

JTA transaction commit causes AssertionFailure: Access a Sealed WorkQueue which has not been sealed --------------------------------------------------------------------------------------------------- Key: HSEARCH-540 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.Final Environment: Hibernate 3.5.2-Final, Spring 3.0.2.RELEASE, MySQL 5.1.34, Atomikos 3.5.13 Reporter: Tom Waterhouse Attachments: hibernate-search-jta-bug.log When we switched our application to use JTA a number of exceptions are generated on transaction commit. Spring is used by the application; the transactions are managed via the Spring class JtaTransactionManager. The Web app and Hibernate Search worked perfectly using JpaTransactionManager. Exception examples: [2010-06-04 09:04:34.391, 49026]ERROR[http-8080-1](AssertionFailure.java:46) - an assertion failure occured (this may indicate a bug in Hibernate) org.hibernate.annotations.common.AssertionFailure: Access a Sealed WorkQueue which has not been sealed [2010-06-04 09:04:34.395, 49030]ERROR[http-8080-1](AssertionFailure.java:50) - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session) org.hibernate.HibernateException: Error while indexing in Hibernate Search (ater transaction completion) The full log file has been attached -- 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

15 years, 8 months

5
31
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2010