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

Charles Chappell (JIRA) noreply at atlassian.com
Fri Jun 22 00:34:53 EDT 2007


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

Charles Chappell updated HSEARCH-88:
------------------------------------

    Attachment: testcase.tar.gz

Test case is implemented as a single .war file.  Requires appropriate drivers for PostGRE on the server side, uses a database connection to test:test at localhost/test by default.  Creates only a couple of tables in the database.

Run the test case, then look at the Application Server Log files.

This produces an assertion failure for every commit after the first.


If anyone needs a fresh pair of eyes looking at the Hibernate Search source, I'd be happy to lend mine for a bit, but please give me an idea of where to look.

In this case, the important files are in the src/java/entity and src/java/servlets folders.  Everything else is Netbeans 5.5.1 infrastructure.  (Sorry for not mentioning until now... I'm using Netbeans 5.5.1)

> 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

        



More information about the hibernate-issues mailing list