[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-540) JTA transaction commit causes AssertionFailure: Access a Sealed WorkQueue which has not been sealed
Fabián Fermín Guerra Soto (JIRA)
noreply at atlassian.com
Wed Aug 18 13:50:42 EDT 2010
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38126#action_38126 ]
Fabián Fermín Guerra Soto commented on HSEARCH-540:
---------------------------------------------------
Greetings,
I'm still facing same problem (even though I've already update search version to 3.2.1):
ERROR - [18 Aug 2010 12:27:46,781] - [ httpSSLWorkerThread-8080-1] - [ JCLLoggerAdapter: 532] - 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
at org.hibernate.search.backend.WorkQueue.getSealedQueue(WorkQueue.java:87)
at org.hibernate.search.backend.impl.BatchedQueueingProcessor.performWorks(BatchedQueueingProcessor.java:280)
at org.hibernate.search.backend.impl.PostTransactionWorkQueueSynchronization.afterCompletion(PostTransactionWorkQueueSynchronization.java:96)
at org.hibernate.search.backend.impl.EventSourceTransactionContext$DelegateToSynchronizationOnAfterTx.doAfterTransactionCompletion(EventSourceTransactionContext.java:176)
Context:
JDK 1.8.0_18 + Glassfish 2.1.1 + Spring 3.0.3 + Hibernate 3.5.3 + Hibernate Search 3.2.1
> 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
> Fix For: 3.2.1, 3.3.0.Alpha1
>
> Attachments: application-context.xml, hibernate-search-jta-bug.log, jta-btm-h2.zip, jta-btm-hibernate.zip, jta-btm.zip, search-context.xml
>
>
> 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list