[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag...
]
Tom Waterhouse commented on HSEARCH-540:
----------------------------------------
Switching to use the Hibernate SessionFactory directly allowed the removal of the flush()
calls and resolved the issue. I'm not sure what the significance of the change is, as
all I've read indicates that Hibernate JPA and JTA should coexist with flush being
called correctly on transaction commit.
Note that in my test case the 'Access a Sealed WorkQueue...' message occurs when
an indexed entity has a one-to-many relationship to a non-indexed entity. This leads me
to believe that the issue is a general Hibernate issue, not a Hibernate Search issue.
I've attached the Hibernate SessionFactory version of the test.
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, jta-btm-hibernate.zip, jta-btm.zip
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