5:38 a.m.
David Bosschaert created AS7-4684:
-------------------------------------
Summary: OSGi subsystem doesn't activate during full integration test
runs
Key: AS7-4684
URL: https://issues.jboss.org/browse/AS7-4684
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Test Suite
Affects Versions: 7.1.2.Final-redhat1
Reporter: David Bosschaert
Assignee: Thomas Diesler
CLI-based tests that attempt to activate the OSGi Framework fail intermittently during
'full' runs of the intergration test suite.
The failure is described here:
http://github.com/jbossas/jboss-as/pull/2039#issuecomment-5157266
It doesn't happen on all platforms and on all runs, but it seems to be fairly
reproducable on Fedora 16.
--
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:40 a.m.
[
https://issues.jboss.org/browse/AS7-4684?page=com.atlassian.jira.plugin.s...
]
David Bosschaert updated AS7-4684:
----------------------------------
Description:
CLI-based tests that attempt to activate the OSGi Framework fail intermittently during
'full' runs of the intergration test suite.
The failure is described here:
http://github.com/jbossas/jboss-as/pull/2039#issuecomment-5157266
It doesn't happen on all platforms and on all runs, but it seems to be fairly
reproducable on Fedora 16.
The failure never occurs when running only the 'osgi' subsection of the
integration tests.
was:
CLI-based tests that attempt to activate the OSGi Framework fail intermittently during
'full' runs of the intergration test suite.
The failure is described here:
http://github.com/jbossas/jboss-as/pull/2039#issuecomment-5157266
It doesn't happen on all platforms and on all runs, but it seems to be fairly
reproducable on Fedora 16.
OSGi subsystem doesn't activate during full integration test
runs
-----------------------------------------------------------------
Key: AS7-4684
URL: https://issues.jboss.org/browse/AS7-4684
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Test Suite
Affects Versions: 7.1.2.Final-redhat1
Reporter: David Bosschaert
Assignee: Thomas Diesler
CLI-based tests that attempt to activate the OSGi Framework fail intermittently during
'full' runs of the intergration test suite.
The failure is described here:
http://github.com/jbossas/jboss-as/pull/2039#issuecomment-5157266
It doesn't happen on all platforms and on all runs, but it seems to be fairly
reproducable on Fedora 16.
The failure never occurs when running only the 'osgi' subsection of the
integration tests.
--
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
6:09 a.m.
[
https://issues.jboss.org/browse/AS7-4684?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler commented on AS7-4684:
-------------------------------------
Lets see a debug log of when this happens.
OSGi subsystem doesn't activate during full integration test
runs
-----------------------------------------------------------------
Key: AS7-4684
URL: https://issues.jboss.org/browse/AS7-4684
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Test Suite
Affects Versions: 7.1.2.Final-redhat1
Reporter: David Bosschaert
Assignee: Thomas Diesler
CLI-based tests that attempt to activate the OSGi Framework fail intermittently during
'full' runs of the intergration test suite.
The failure is described here:
http://github.com/jbossas/jboss-as/pull/2039#issuecomment-5157266
It doesn't happen on all platforms and on all runs, but it seems to be fairly
reproducable on Fedora 16.
The failure never occurs when running only the 'osgi' subsection of the
integration tests.
--
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:16 a.m.
[
https://issues.jboss.org/browse/AS7-4684?page=com.atlassian.jira.plugin.s...
]
David Bosschaert commented on AS7-4684:
---------------------------------------
I have shared debug logs of a run exposing the problem here:
* http://dl.dropbox.com/u/1151396/as7-4684-logs/server.log
* http://dl.dropbox.com/u/1151396/as7-4684-logs/test.log
To reproduce, run on branch http://github.com/bosschaert/jboss-as/tree/as7-3556-3 the
following command:
{code} testsuite/integration/basic$ mvn install{code}
OSGi subsystem doesn't activate during full integration test
runs
-----------------------------------------------------------------
Key: AS7-4684
URL: https://issues.jboss.org/browse/AS7-4684
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Test Suite
Affects Versions: 7.1.2.Final-redhat1
Reporter: David Bosschaert
Assignee: Thomas Diesler
CLI-based tests that attempt to activate the OSGi Framework fail intermittently during
'full' runs of the intergration test suite.
The failure is described here:
http://github.com/jbossas/jboss-as/pull/2039#issuecomment-5157266
It doesn't happen on all platforms and on all runs, but it seems to be fairly
reproducable on Fedora 16.
The failure never occurs when running only the 'osgi' subsection of the
integration tests.
--
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:10 a.m.
[
https://issues.jboss.org/browse/AS7-4684?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler commented on AS7-4684:
-------------------------------------
This branch builds on an outdated version of the osgi subsystem. We since had a component
freeze with Final versions of all osgi binaries - please rebase. Also your log shows
multiple runs that are hours apart that use different framework versions - you can set the
append flag to false.
I believe this
{code}
FutureServiceValue<?> fsv = new FutureServiceValue(svc);
try {
// Wait for the service to be up before returning.
fsv.get(20, TimeUnit.SECONDS);
} catch (Exception e) {
throw new OperationFailedException(e, operation);
}
{code}
should be done with a verification handler.
OSGi subsystem doesn't activate during full integration test
runs
-----------------------------------------------------------------
Key: AS7-4684
URL: https://issues.jboss.org/browse/AS7-4684
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Test Suite
Affects Versions: 7.1.2.Final-redhat1
Reporter: David Bosschaert
Assignee: Thomas Diesler
CLI-based tests that attempt to activate the OSGi Framework fail intermittently during
'full' runs of the intergration test suite.
The failure is described here:
http://github.com/jbossas/jboss-as/pull/2039#issuecomment-5157266
It doesn't happen on all platforms and on all runs, but it seems to be fairly
reproducable on Fedora 16.
The failure never occurs when running only the 'osgi' subsection of the
integration tests.
--
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:08 a.m.
[
https://issues.jboss.org/browse/AS7-4684?page=com.atlassian.jira.plugin.s...
]
David Bosschaert commented on AS7-4684:
---------------------------------------
I've changed the tests to use the direct DMR management APIs instead of the CLI
wrapper and that seems to help... I'll give it another few runs to see whether its
reliable.
OSGi subsystem doesn't activate during full integration test
runs
-----------------------------------------------------------------
Key: AS7-4684
URL: https://issues.jboss.org/browse/AS7-4684
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Test Suite
Affects Versions: 7.1.2.Final-redhat1
Reporter: David Bosschaert
Assignee: Thomas Diesler
CLI-based tests that attempt to activate the OSGi Framework fail intermittently during
'full' runs of the intergration test suite.
The failure is described here:
http://github.com/jbossas/jboss-as/pull/2039#issuecomment-5157266
It doesn't happen on all platforms and on all runs, but it seems to be fairly
reproducable on Fedora 16.
The failure never occurs when running only the 'osgi' subsection of the
integration tests.
--
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
4:18 p.m.
[
https://issues.jboss.org/browse/AS7-4684?page=com.atlassian.jira.plugin.s...
]
David Bosschaert resolved AS7-4684.
-----------------------------------
Resolution: Done
Migrating to DMR-based tests from CLI-based tests resolved the issue.
OSGi subsystem doesn't activate during full integration test
runs
-----------------------------------------------------------------
Key: AS7-4684
URL: https://issues.jboss.org/browse/AS7-4684
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Test Suite
Affects Versions: 7.1.2.Final (EAP)
Reporter: David Bosschaert
Assignee: Thomas Diesler
CLI-based tests that attempt to activate the OSGi Framework fail intermittently during
'full' runs of the intergration test suite.
The failure is described here:
http://github.com/jbossas/jboss-as/pull/2039#issuecomment-5157266
It doesn't happen on all platforms and on all runs, but it seems to be fairly
reproducable on Fedora 16.
The failure never occurs when running only the 'osgi' subsection of the
integration tests.
--
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
4570
days inactive
4574
days old
6 comments
2 participants
participants (2)
-
David Bosschaert (JIRA) -
Thomas Diesler (JIRA)