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

[Hibernate-JIRA] Created:...

[Hibernate-JIRA] Closed:...

Tom Waterhouse (JIRA)

Friday, 4 June 2010 Fri, 4 Jun '10

11:29 p.m.

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

Show replies by date

Emmanuel Bernard (JIRA)

Friday, 18 June Fri, 18 Jun

2:32 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard commented on HSEARCH-540: ------------------------------------------ There could be multiple reasons: - your Spring configuration is wrong - your Hibernate configuration is wrong (in particular use the correct TransactionManager) - Atomikos does not properly call Synchronization#beforeTransaction In all cases, you are likely having problems with Hibernate too as the auto flush is no longer called either (unless Spring does some additional stuff, I don't know).

...

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

Tom Waterhouse (JIRA)

Tuesday, 22 June Tue, 22 Jun

9:58 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Tom Waterhouse commented on HSEARCH-540: ---------------------------------------- I have two test cases using the application entities. One test case works, one test case doesn't. Given that, my expectation is that Spring is configured properly for JTA transactions, and Hibernate is configured properly as well. I also switched to Bitronix to rule out Atomikos as the issue. For the working test WorkQueue.setSealedQueue() is called, therefore the sealedQueue is set. For the failing test WorkQueue.setSealedQueue() is not called. I am currently trying to determine why WorkQueue.setSealedQueue() isn't called for the failing test case.

...

HL (JIRA)

Thursday, 24 June Thu, 24 Jun

10:30 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] HL commented on HSEARCH-540: ---------------------------- Hi Tom Waterhouse, I have exactly the same issue. Have you found a solution yet? My case is this, when test standalone, no exception thrown, in web container, it threw exception during update but not persist.

...

HL (JIRA)

Monday, 28 June Mon, 28 Jun

10:54 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] HL commented on HSEARCH-540: ---------------------------- I solved my issue. I was using jdbc transaction manager instead of hibernate transaction manager.

...

Tom Waterhouse (JIRA)

Tuesday, 6 July Tue, 6 Jul

9:31 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Tom Waterhouse commented on HSEARCH-540: ---------------------------------------- The issue goes away with a call to EntityManager.flush() before transaction commit. With the Spring JPA transaction manager flush is called automatically before transaction commit. With JTA it is not called until after transaction commit. With a manual call to EntityManager.flush() after EntityManager.merge() the respective Hibernate Search events are called in proper order with regards to transaction synchronization.

...

Emmanuel Bernard (JIRA)

10:21 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard commented on HSEARCH-540: ------------------------------------------ Then that's definitively a configuration issue or a Spring bug because Hibernate does stick the flush operation in the before commit phase of JTA.

...

Tom Waterhouse (JIRA)

Wednesday, 7 July Wed, 7 Jul

9:51 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Tom Waterhouse commented on HSEARCH-540: ---------------------------------------- I noticed the following in the log file. Related to the lack of flushing before transaction commit? [2010-38-07 07:38:47.346, 0]WARN [main](Ejb3Configuration.java:1230) - Defining hibernate.transaction.flush_before_completion=true ignored in HEM

...

Emmanuel Bernard (JIRA)

9:54 a.m.

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

...

Tom Waterhouse (JIRA)

9:58 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Tom Waterhouse updated HSEARCH-540: ----------------------------------- Attachment: jta-btm.zip Simple test project used to reproduce the issue

...

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

j nadler (JIRA)

Friday, 9 July Fri, 9 Jul

6:51 p.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] j nadler commented on HSEARCH-540: ---------------------------------- I'm seeing this problem as well. I'm guessing that it is a Hibernate Search bug. It only happens on one of the entities in our app, so I'm guessing that it is very sensitive to the details of the entity mapping. Anyway I may be able to provide another data point here...

...

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

j nadler (JIRA)

Saturday, 10 July Sat, 10 Jul

3:49 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] j nadler commented on HSEARCH-540: ---------------------------------- Interesting: Tom said that the problem went away with an explicit flush. I was trying to use hibernate.transaction.flush_before_completion=true, but I notice that Ejb3Configuration clobbers that setting with a message like "flush_before_completion=true ignored in HEM" With hibernate debug logging enabled, it appears that no flush is happening before commit in my configuration. In a 'standalone JTA' environment (Tomcat, Hibernate as a JPA provider, Spring manages JTA transactions using either JOTM or Atomikos, both give the same result) how should the flush-before-commit happen? In my case at least, this seems to be at the root of the problem. I'd like to turn flush_before_completion on, but Ejb3Configuration won't let me. That leads me to believe that the Hibernate Entity Manager authors expected the automatic flush before commit to happen in some other way. From my experience, in this particular stack there is no way to make it happen. I bet if I switched to pure hibernate (ditch the JPA, keep everything else, leaving Tomcat, Hibernate, Spring, JOTM) that it would work fine because I could then turn on flush_before_completion. Ditching JPA is not the right solution, of course.

...

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

Tom Waterhouse (JIRA)

6:04 p.m.

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

[ 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

Tom Waterhouse (JIRA)

6:04 p.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Tom Waterhouse updated HSEARCH-540: ----------------------------------- Attachment: jta-btm-hibernate.zip

...

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

Emmanuel Bernard (JIRA)

Sunday, 11 July Sun, 11 Jul

11:01 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard commented on HSEARCH-540: ------------------------------------------ We've found the probable cause of the issue. The same behavior was found in envers and analyzed by Adam. Basically, Hibernate Core behaves a bit inconsistently between a resource-local tx and a JTA tx. To compensate we use a different before tx register mechanism but it turns out it leads to problems as the flush operation is called after the listeners of HSearch / Envers. Check the hibernate-dev mailing list (July 10th 2010) [hibernate-dev] Exceptions thrown in a tx synchronization are eaten for an ongoing discussion.

...

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

j nadler (JIRA)

Monday, 12 July Mon, 12 Jul

12:53 p.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] j nadler commented on HSEARCH-540: ---------------------------------- Thanks Emmanuel. When you know more about the solution will you update us here? We are now trying to decide whether to ditch JPA entirely to work around this issue. If a fix will be available within a few weeks, we will most likely decide to wait.

...

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

Emmanuel Bernard (JIRA)

1:39 p.m.

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

...

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

Emmanuel Bernard (JIRA)

Tuesday, 13 July Tue, 13 Jul

8:20 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard commented on HSEARCH-540: ------------------------------------------ Tom, I'm trying to run your test but it requires that I run MySQL on a separate process. Do you know if it's doable to make it run on H2 to get an in memory solution. I'd like to make it into the unit test suite eventually but I'll have to change a bunch of stuff, the first one being the separate DB requirement.

...

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

Emmanuel Bernard (JIRA)

10:31 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard commented on HSEARCH-540: ------------------------------------------ Hi Tom, I've committed a probable fix (r19943) and pushed it in https://repository.jboss.org/nexus/content/repositories/snapshots//org/hi... can you give it a try and let me know if that fixes your problem?

...

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

Tom Waterhouse (JIRA)

2:56 p.m.

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

...

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-h2.zip, 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

Tom Waterhouse (JIRA)

3:01 p.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Tom Waterhouse commented on HSEARCH-540: ---------------------------------------- The 3.3.0-SNAPSHOT build does resolve the sealed queue issue (testMuffins). It looks like another issue exists (testDoughnuts): javax.persistence.PersistenceException: java.lang.UnsupportedOperationException at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:1071) at bitronix.tm.BitronixTransaction.fireBeforeCompletionEvent(BitronixTransaction.java:430) at bitronix.tm.BitronixTransaction.commit(BitronixTransaction.java:173) at bitronix.tm.BitronixTransactionManager.commit(BitronixTransactionManager.java:104) at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1009) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754) at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723) at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:375) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:625) at org.foobar.BoxDAO$$EnhancerByCGLIB$$9d21c0d7.merge(<generated>) at org.foobar.BoxTest.testDoughnuts(BoxTest.java:47) . . . Caused by: java.lang.UnsupportedOperationException at java.util.AbstractList.add(AbstractList.java:131) at java.util.AbstractList.add(AbstractList.java:91) at org.hibernate.search.backend.WorkQueue.add(WorkQueue.java:59) at org.hibernate.search.backend.impl.BatchedQueueingProcessor.add(BatchedQueueingProcessor.java:130) at org.hibernate.search.backend.impl.PostTransactionWorkQueueSynchronization.add(PostTransactionWorkQueueSynchronization.java:68) at org.hibernate.search.backend.impl.TransactionalWorker.performWork(TransactionalWorker.java:82) at org.hibernate.search.event.FullTextIndexEventListener.processWork(FullTextIndexEventListener.java:181) at org.hibernate.search.event.FullTextIndexEventListener.processCollectionEvent(FullTextIndexEventListener.java:228) at org.hibernate.search.event.FullTextIndexEventListener.onPostRemoveCollection(FullTextIndexEventListener.java:202) at org.hibernate.action.CollectionRemoveAction.postRemove(CollectionRemoveAction.java:146) at org.hibernate.action.CollectionRemoveAction.execute(CollectionRemoveAction.java:119) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:268) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:260) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:181) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:51) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1206) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:375) at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:1057) ... 42 more

...

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-h2.zip, 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

Emmanuel Bernard (JIRA)

Wednesday, 14 July Wed, 14 Jul

1:43 p.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard commented on HSEARCH-540: ------------------------------------------ Hi Tom, Tanks for the h2 test. I've fixed the subsequent issue and I run your test on my side. Can you double check and run it in your environment? I've pushed a new snapshot at https://repository.jboss.org/nexus/content/repositories/snapshots//org/hi... There is a small twist, we have upgraded HSearch to depend on Hibernate Core 3.6.0-SNAPSHOT. In your small test the migration was trivial (jsut the deps version changed). Let me know if you have any issue. If that works for you, we will backport the bug fix to HSearch 3.2.x. That was a nasty bug.

...

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-h2.zip, 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

Emmanuel Bernard (JIRA)

1:43 p.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard edited comment on HSEARCH-540 at 7/14/10 1:42 PM: ------------------------------------------------------------------- Hi Tom, Thanks for the h2 test. I've fixed the subsequent issue and I run your test on my side. Can you double check and run it in your environment? I've pushed a new snapshot at https://repository.jboss.org/nexus/content/repositories/snapshots//org/hi... There is a small twist, we have upgraded HSearch to depend on Hibernate Core 3.6.0-SNAPSHOT. In your small test the migration was trivial (jsut the deps version changed). Let me know if you have any issue. If that works for you, we will backport the bug fix to HSearch 3.2.x. That was a nasty bug. was (Author: emmanuel): Hi Tom, Tanks for the h2 test. I've fixed the subsequent issue and I run your test on my side. Can you double check and run it in your environment? I've pushed a new snapshot at https://repository.jboss.org/nexus/content/repositories/snapshots//org/hi... There is a small twist, we have upgraded HSearch to depend on Hibernate Core 3.6.0-SNAPSHOT. In your small test the migration was trivial (jsut the deps version changed). Let me know if you have any issue. If that works for you, we will backport the bug fix to HSearch 3.2.x. That was a nasty bug.

...

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-h2.zip, 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

Tom Waterhouse (JIRA)

11:38 p.m.

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

...

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-h2.zip, 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

Emmanuel Bernard (JIRA)

Monday, 19 July Mon, 19 Jul

3:17 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard commented on HSEARCH-540: ------------------------------------------ Hi Tom, another question. Can I consider what's inside jta-btm-h2.zip to be released as LGPL to the Hibernate project. I did write an integration test module based on it and would like to commit it. If the answer is yes, let me know in a comment here. And ideally log to jboss.org then go to http://cla.jboss.org to sign a contributor agreement and let me know when you're done - this agreement is in essence like the Apache one and clarify your contribution.

...

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-h2.zip, 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

Tom Waterhouse (JIRA)

3:10 p.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Tom Waterhouse commented on HSEARCH-540: ---------------------------------------- Emmanuel, yes jta-btm-h2.zip can be released as LGPL to the Hibernate project. I've signed the Individual Contributors License Agreement.

...

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-h2.zip, 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

Emmanuel Bernard (JIRA)

Tuesday, 20 July Tue, 20 Jul

4:54 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard resolved HSEARCH-540. -------------------------------------- Resolution: Fixed Fix Version/s: 3.3.0 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 Attachments: hibernate-search-jta-bug.log, jta-btm-h2.zip, 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

Emmanuel Bernard (JIRA)

4:54 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard commented on HSEARCH-540: ------------------------------------------ Thank you Tom. I've pushed the integration module to SVN. I've also committed the fix to Branch_3_2 and pushed a snapshot to https://repository.jboss.org/nexus/content/groups/public-jboss/org/hibern...

...

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 Attachments: hibernate-search-jta-bug.log, jta-btm-h2.zip, 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

Emmanuel Bernard (JIRA)

Monday, 26 July Mon, 26 Jul

5:03 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard updated HSEARCH-540: ------------------------------------- Fix Version/s: (was: 3.2.1) (was: 3.3.0) 3.3.0.Alpha1

...

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: hibernate-search-jta-bug.log, jta-btm-h2.zip, 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

Emmanuel Bernard (JIRA)

5:04 a.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard updated HSEARCH-540: ------------------------------------- Fix Version/s: 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: hibernate-search-jta-bug.log, jta-btm-h2.zip, 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

Fabián Fermín Guerra Soto (JIRA)

Wednesday, 18 August Wed, 18 Aug

12:50 p.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] 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

Emmanuel Bernard (JIRA)

12:59 p.m.

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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-540?pag... ] Emmanuel Bernard commented on HSEARCH-540: ------------------------------------------ Hi Fabián, Can you try and create a minimal test case based on or cloned from http://anonsvn.jboss.org/repos/hibernate/search/trunk/hibernate-search-in... This kind of issue proves to be very hard to reproduce for the person not with the issue at hand. Also open a new JIRA as its likely a different problem.

...

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

5198

days inactive

5272

days old

hibernate-issues@lists.jboss.org

Manage subscription

31 comments

5 participants

tags (0)

participants (5)

Emmanuel Bernard (JIRA)
Fabián Fermín Guerra Soto (JIRA)
HL (JIRA)
j nadler (JIRA)
Tom Waterhouse (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

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