[dna-issues] [JBoss JIRA] Commented: (DNA-198) JackrabbitDerbyStressTest throws exceptions intermittently without failing

[Randall Hauch (JIRA)]

    [ https://jira.jboss.org/jira/browse/DNA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12424674#action_12424674 ] 

Randall Hauch commented on DNA-198:
-----------------------------------

For the record, this was just posted to the JR list by Thomas Müller:

  > (it would not attempt to auto-delete the .lock file from what we 
  > were experiencing).
  Maybe that was using an old version of Jackrabbit (not sure), but in
  1.3 and 1.4 you should not delete the .lock file, it is deleted
  automatically. If it is not deleted automatically, this is an
  indication that the repository is still open (in another process, or
  within the same process in another classloader). 

(http://www.nabble.com/Re%3A-Issues-while-importing.-p18953711.html)

>From this description, my hypothesis is that the indexing activity (again, should be done in a separate thread) is not yet done with the session when the test's afterEach() method deletes all of the files (including the .lock file).  Therefore, this would also help explain why, with indexing turned off, there are no more problems.

> JackrabbitDerbyStressTest throws exceptions intermittently without failing
> --------------------------------------------------------------------------
>
>                 Key: DNA-198
>                 URL: https://jira.jboss.org/jira/browse/DNA-198
>             Project: DNA
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: 0.1
>            Reporter: Johnny Verhaeg
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.2
>
>         Attachments: JackRabbitDerbyStressTestFailure.txt
>
>
> Attached file contains a sample of output.  The output shows several errors are logged beginning with the 1000 node test, but I've seen that particular test work sometimes without the error being logged (when run along with the rest of the test class).  If each test method is run separately, each test seems to pretty consistently run without logged errors.
> Note that this problem does not result in a test failure.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira