[seam-issues] [JBoss JIRA] (SEAMJCR-24) JcrCDIEventListenerJackrabbitTest sometimes fails on Jenkins

[John Ament (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/SEAMJCR-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637845#comment-12637845 ] 

John Ament commented on SEAMJCR-24:
-----------------------------------

Marek, do you want to increase the time to 10 seconds, see if it works better?  ModeShape runs background threads for a lot of this, which is why we need to put a sleep in.
                
> JcrCDIEventListenerJackrabbitTest sometimes fails on Jenkins
> ------------------------------------------------------------
>
>                 Key: SEAMJCR-24
>                 URL: https://issues.jboss.org/browse/SEAMJCR-24
>             Project: Seam JCR
>          Issue Type: Bug
>          Components: JackRabbit Integration
>    Affects Versions: 3.1.0.Beta4
>            Reporter: Marek Schmidt
>         Attachments: org.jboss.seam.jcr.test.common.events.JcrCDIEventListenerJackrabbitTest.testOnEventAdded.txt
>
>
> JcrCDIEventListenerJackrabbitTest sometimes fails on Jenkins,
> A comment in the test reads:
> {noformat}
>  // ModeShape uses background threads for event firing and similar
>  // activities.
>  // let's give it 5 seconds to run, then check the bags.
>  Thread.sleep(5000);
>  // Check that node was added
>  assertEquals(1, counter.getCountForType(Event.NODE_ADDED));
> {noformat}
> so perhaps the 5 seconds limit is just not enoough? 
> Also note the attached log in which it appears the repository had been shut down before the assertion was made, which might suggest that waiting longer probably wouldn't help and that the event just didn't happen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira