as7-master-testsuite-ip6 - Build # 5684 - Failure!
by ci-builds＠redhat.com
as7-master-testsuite-ip6 - Build # 5684 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/as7-master-testsuite-ip6/5684
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-testsui...
Test summary:
1 tests failed.
FAILED: org.jboss.as.test.integration.osgi.stilts.StompletTestCase.org.jboss.as.test.integration.osgi.stilts.StompletTestCase
Error Message:
java.lang.Exception: {"JBAS014671: Failed services" => {"jboss.deployment.unit.stomplet-server-provider.Activate" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.stomplet-server-provider.Activate: JBAS011968: Cannot start bundle: stomplet-server-provider:0.0.0 Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: stilts-stomplet-server-bundle:0.1.26 Caused by: java.lang.NullPointerException"}}
11 years, 10 months
jgroups 3.2.2.Final
by Ales Justin
Can we get JGroups 3.2.2.Final into AS7 upstream before/during weekend?
It's a minor change wrt 3.2.1.Final, but it does fix an ugly leak,
which prevents CapeDwarf testsuite to fully run.
Where I would like to do an initial CD release before Monday -- off to China then. :-)
-Ales
11 years, 10 months
Adding the ability to run the OSGi TCK with AS7
by David Bosschaert
As many know - AS7 is also an OSGi Framework meaning that it implements
the OSGi Core Specifications.
Additionally native JBoss support for more and more OSGi Enterprise
Specifications is being added. Examples are:
* The OSGi HttpService Specification (as7-5083)
* The OSGi WebApplication Specification (as7-5235)
* OSGi JPA support (as7-5476)
* other specs are also looked at
For everything that implements an OSGi spec there is also an OSGi TCK
testsuite. Over the past while I've been looking at getting AS7 to run
under the OSGi TCK. This is specifically needed when you want to check
that the above implementations are actually compliant with the specs.
To be able to run AS7 under the OSGi TCK 2 things had to be done:
* OSGi in AS7 had to be enhanced to support the OSGi Launcher API [1].
This is what the TCK uses to launch a framework.
* The TCK configuration files need to be tweaked so that it runs with
AS7 (instead of the RI).
I've implemented these two in
http://github.com/bosschaert/jboss-as/commit/8de4742e3f7bef059c2d12137c36...
I've added the TCK integration to the jboss-as/osgi/tck subtree. It's
fairly small as its mostly configuration and having it in jboss-as means
that we can easily kick off a tck run in hudson or from the commandline
for any AS build. It effectively gets us an additional bunch of system
tests for the (Enterprise) OSGi compliant components.
No changes to the product (build directory). The launcher API is not yet
included in the product, although we could decide to include it if we
think that makes sense.
I would like to file a pull request for this soon. Hope this works for
others. The associated JIRA is https://issues.jboss.org/browse/AS7-5639
Thanks,
David
[1]
http://www.osgi.org/javadoc/r4v42/org/osgi/framework/launch/package-summa...
11 years, 10 months
as7-master-testsuite-ip6 - Build # 5630 - Failure!
by ci-builds＠redhat.com
as7-master-testsuite-ip6 - Build # 5630 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/as7-master-testsuite-ip6/5630
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-testsui...
Test summary:
1 tests failed.
FAILED: org.jboss.as.test.integration.osgi.stilts.StompletTestCase.org.jboss.as.test.integration.osgi.stilts.StompletTestCase
Error Message:
java.lang.Exception: {"JBAS014671: Failed services" => {"jboss.deployment.unit.stomplet-server-provider.Activate" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.stomplet-server-provider.Activate: JBAS011968: Cannot start bundle: stomplet-server-provider:0.0.0 Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: stilts-stomplet-server-bundle:0.1.26 Caused by: java.lang.NullPointerException"}}
11 years, 10 months
