[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-88) Workspace.getIndexReader AssertionFailure: Tries to read for update a index while a writer is accessed

[Charles Chappell (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_27306 ] 

Charles Chappell commented on HSEARCH-88:
-----------------------------------------

Last comment of the day for me (back to my main line of work):

If you create a second Login class that has no Hibernate Search annotations, and search in the same way as above, it still causes assertion failures.  This may give some clue into what's going on, as it seems like this issue is coming up during a find transaction that also fetches a Hibernate Search indexed entity.

I'm not sure what the limits are of this yet, but the case I've supplied should be complete enough to play with this.

If I figure out what's actually causing my application to fail, I'll add it to the test case.  I'm pretty sure it's hibernate search though, as there were no problems in this section of code until I started annotating the Person and Login entities as Indexed.  This test case is showing relatively harmless failures, as the data is still retrieved either way.  In my EJB, the data isn't retrieved, causing failures.

> Workspace.getIndexReader AssertionFailure: Tries to read for update a index while a writer is accessed
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HSEARCH-88
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-88
>             Project: Hibernate Search
>          Issue Type: Bug
>    Affects Versions: 3.0.0.beta3
>         Environment: Hibernate 3.2.4.sp1, PostGRESQL
>            Reporter: Charles Chappell
>            Priority: Minor
>         Attachments: Login.java, testcase.tar.gz
>
>
> May be an application server interaction.
> Somewhat sporatic, but always in the same places in my code.  Basically I had one class that created an entity exit via NullPointerException, (Database updates were successful) and a second attempt to read the same data was made, and failed due to this assertion.  The only connection to Hibernate Search is via the Annotations/Runtime, nowhere in this process did I directly use Hibernate Search.
> I'll attempt to produce test code, since this is the simplest case that I've gotten this assertion failure in.
> Application Server is Glassfish, reproducable both on OSX and Solaris 10 Intel.

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