10:03 a.m.
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
Priority: Minor
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?
--
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
10:03 a.m.
[
https://issues.jboss.org/browse/SEAMJCR-24?page=com.atlassian.jira.plugin...
]
Marek Schmidt updated SEAMJCR-24:
---------------------------------
Attachment:
org.jboss.seam.jcr.test.common.events.JcrCDIEventListenerJackrabbitTest.testOnEventAdded.txt
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
Priority: Minor
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?
--
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
10:38 a.m.
[
https://issues.jboss.org/browse/SEAMJCR-24?page=com.atlassian.jira.plugin...
]
Marek Schmidt updated SEAMJCR-24:
---------------------------------
Priority: Major (was: Minor)
Description:
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.
was:
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?
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
8:35 p.m.
[
https://issues.jboss.org/browse/SEAMJCR-24?page=com.atlassian.jira.plugin...
]
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
7:49 a.m.
[
https://issues.jboss.org/browse/SEAMJCR-24?page=com.atlassian.jira.plugin...
]
Marek Schmidt commented on SEAMJCR-24:
--------------------------------------
I have updated the wait time to 10 seconds and was able to reproduce it again on the same
machine:
{noformat}
08:38:18,239 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 39 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - Starting
repository...
08:38:18,242 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 42 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem -
LocalFileSystem initialized at path target/repository
08:38:18,309 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 108 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.nodetype.NodeTypeRegistry - no
custom node type definitions found
08:38:18,316 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 116 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem -
LocalFileSystem initialized at path target/version
08:38:19,562 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 1362 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - initializing
workspace 'default'...
08:38:19,567 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 1367 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem -
LocalFileSystem initialized at path target/workspaces/default
08:38:20,070 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 1870 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index
initialized: target/repository/index Version: 3
08:38:20,148 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 1947 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index
initialized: target/workspaces/default/index Version: 3
08:38:20,149 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 1949 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace
'default' initialized
08:38:20,156 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 1955 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - SecurityManager
= class org.apache.jackrabbit.core.security.simple.SimpleSecurityManager
08:38:20,157 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 1957 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - initializing
workspace 'security'...
08:38:20,157 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 1957 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem -
LocalFileSystem initialized at path target/workspaces/security
08:38:20,435 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2234 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index
initialized: target/workspaces/security/index Version: 3
08:38:20,436 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2236 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace
'security' initialized
08:38:20,438 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2238 [RMI TCP
Connection(13)-127.0.0.1] INFO
org.apache.jackrabbit.core.security.simple.SimpleSecurityManager - init: using Repository
LoginModule configuration for Jackrabbit
08:38:20,447 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2247 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - Repository
started (2208ms)
08:38:20,448 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2248 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.TransientRepository - Transient
repository initialized
08:38:20,479 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2279 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.TransientRepository - Session
opened
08:38:20,611 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2411 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.TransientRepository - Session
closed
08:38:20,612 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2412 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - Shutting down
repository...
08:38:20,616 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2416 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index
closed: target/repository/index
08:38:20,617 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2417 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - shutting down
workspace 'default'...
08:38:20,620 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2420 [RMI TCP
Connection(13)-127.0.0.1] INFO
org.apache.jackrabbit.core.observation.ObservationDispatcher - Notification of
EventListeners stopped.
08:38:20,697 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2497 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index
closed: target/workspaces/default/index
08:38:20,730 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2529 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.util.db.DerbyConnectionHelper -
Database 'target/workspaces/default/db' shutdown.
08:38:20,733 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2533 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace
'default' has been shutdown
08:38:20,734 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2534 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - shutting down
workspace 'security'...
08:38:20,735 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2535 [RMI TCP
Connection(13)-127.0.0.1] INFO
org.apache.jackrabbit.core.observation.ObservationDispatcher - Notification of
EventListeners stopped.
08:38:20,737 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2537 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index
closed: target/workspaces/security/index
08:38:20,749 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2548 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.util.db.DerbyConnectionHelper -
Database 'target/workspaces/security/db' shutdown.
08:38:20,749 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2549 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace
'security' has been shutdown
08:38:20,763 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2563 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.util.db.DerbyConnectionHelper -
Database 'target/version/db' shutdown.
08:38:20,766 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2566 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.RepositoryImpl - Repository has
been shutdown
08:38:20,769 ERROR [stderr] (RMI TCP Connection(13)-127.0.0.1) 2569 [RMI TCP
Connection(13)-127.0.0.1] INFO org.apache.jackrabbit.core.TransientRepository - Transient
repository shut down
08:38:30,795 ERROR [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (RMI TCP
Connection(13)-127.0.0.1) Failed:
org.jboss.seam.jcr.test.common.events.JcrCDIEventListenerJackrabbitTest.testOnEventAdded:
java.lang.AssertionError: expected:<1> but was:<0>
{noformat}
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
2:20 a.m.
[
https://issues.jboss.org/browse/SEAMJCR-24?page=com.atlassian.jira.plugin...
]
Marek Schmidt updated SEAMJCR-24:
---------------------------------
Affects Version/s: 3.1.0.Beta5
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, 3.1.0.Beta5
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
5:09 a.m.
[
https://issues.jboss.org/browse/SEAMJCR-24?page=com.atlassian.jira.plugin...
]
Marek Schmidt commented on SEAMJCR-24:
--------------------------------------
Increasing it to 60 seconds doesn't seem to make a difference. The error happens
consistently with ~50% probability on jenkins slaves. I cannot reproduce it locally. This
is just a wild guess, but is it possible that the event isn't observed if it was fired
on some different background thread? That would explain why I can only reproduce it on
jenkins slaves, which are all >1 CPU.
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, 3.1.0.Beta5
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
10:32 a.m.
[
https://issues.jboss.org/browse/SEAMJCR-24?page=com.atlassian.jira.plugin...
]
Marek Schmidt updated SEAMJCR-24:
---------------------------------
Affects Version/s: 3.1.0.CR1
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, 3.1.0.Beta5, 3.1.0.CR1
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
4566
days inactive
4603
days old
7 comments
4 participants
participants (4)
-
John Ament (Commented) (JIRA) -
Marek Schmidt (Commented) (JIRA)
-
Marek Schmidt (Created) (JIRA)
-
Marek Schmidt (Updated) (JIRA)