[
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