[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
[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
[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