JBWS-3073 & Hudson
by Alessio Soldano
Folks,
I've re-configured hudson on jbossws.jboss.org:8180/hudson according to
the changes for JBWS-3073. The changes have been committed on
jbossws-framework/hudson trunk. Basically we now have different jobs for
JBossWS-CXF with and without Spring support. The spring flavour of those
jobs installs jbossws-cxf with the -Dspring=true property for including
Spring libraries on the server and uses the -Pspring profile for adding
spring artifacts to the client classpath.
Further documentation on JBWS-3073 coming soon.
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
15 years, 11 months
Hudson regressions
by Alessio Soldano
Hi Folks,
I've spent some time today looking at the hudson failures we had at
http://jbossws.jboss.org:8180/hudson/
The failures in SecurityDomainTestCase (all stacks) are related to
JBAS-8060.
We had many OOME with CXF stack that went unnoticed as the virtual
machine did not crash and Maven reported successful builds nevertheless;
fixed the issue and -more important- the hudson jobs for detecting such
risky situations.
Finally, the webserviceref related failures on hudson are due to a
refactoring in jboss-classloading/jboss-classloader projects; we
basically have a missing dependency in the testsuite modules... instead
of adding yet another dependency there, I'm refactoring that for using
the AS 6 depchain module. This would allow us to automatically get the
correct and complete dependencies directly from the target container. No
more editing there... I'm committing a first cut for the CXF stack only
later this evening or early tomorrow, I'll then go on tomorrow after
dealing with the CXF 2.2.9 update.
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
15 years, 12 months
JBossWS 3.3.1 release next week
by Alessio Soldano
Hi folks,
I've just created branches for JBossWS 3.3.1 (stacks only) which I do
plan to release next week (hopefully on Tuesday).
The main reasons for this early 3.3.1 release are:
- the need to include the Apache CXF 2.2.9 upgrade which should be out
early next week (afaics the vote phase for it should be completed by end
of today) (JBWS-3057)
- the need to fix the binary distribution installation, which fails with
3.3.0 against vanilla AS versions (JBWS-3048)
I've started a Hudson instance on http://jbossws.jboss.org:8280/hudson/
for 3.3.1. We'll manually trigger job runs after the CXF 2.2.9 update.
No other fixes/issues should be committed to the 3.3.1 branches unless
for fixing testsuite failures reported by Hudson.
The development for JBossWS 4.0 goes on on trunk as usual.
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
16 years
Re: [jbossws-dev] CXF 2.2.9
by Sergey Beryozkin
Hi Alessio
>> Reason: POM 'org.jboss.spec:jboss-javaee6-specs-bom' not found in
>> repository: Unable to download the artifact from any repository
>> "
>Do you have the jboss repository properly configured in your maven
>settings? Is this still outstanding? I need to verify in any case.
>Btw, on a related topic, yesterday I saw a thread on the AS dev list
>(jboss-development(a)lists.jboss.org) started by Paul Gier ([jboss-dev]
>Nexus configuration changes, 2nd June) talking about updates on the
>jboss m2 repository configuration, you might want to check that too.
Is there a wiki document available ? I've checked the community build wiki, was not able to find anything specific.
Also got subscribed to the jboss-dev list.
> Anyway, when running with jboss600 I see :
>
> Tests in error:
>
> testMessagingClient(org.jboss.test.ws.jaxws.samples.jmstransport.FromJavaJMSTransportTestCase)
> testMessagingClient(org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase)
> testJMSEndpointPort(org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase)
> testHTTPEndpointPort(org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase)
> test(org.jboss.test.ws.jaxws.samples.wssePolicy.UsernameTestCase)
> testServletClient(org.jboss.test.ws.jaxws.cxf.webserviceref.WebServiceRefServletTestCase)
>
I've just rebuilt M3 and after deploying into it I'm still seeing the same tests failing, running from the jbosscxf root.
>Btw, I currently see these 5 failures against AS6 M3:
>Tests in error:
>testTarget(org.jboss.test.ws.jaxws.smoke.tools.WSConsumerTestCase)
>testAdditionalHeaders(org.jboss.test.ws.jaxws.smoke.tools.WSConsumerTestCase)
This one passes for me,
>testAddItem(org.jboss.test.ws.jaxws.samples.addressing.AddressingStatefulTestCase)
>testGetItems(org.jboss.test.ws.jaxws.samples.addressing.AddressingStatefulTestCase)
>testCheckout(org.jboss.test.ws.jaxws.samples.addressing.AddressingStatefulTestCase)
Failing for me too
thanks, Sergey
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
_______________________________________________
jbossws-dev mailing list
jbossws-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-dev
16 years
Re: [jbossws-dev] CXF 2.2.9
by Alessio Soldano
Sergey Beryozkin wrote:
> ok, after installing JCE unlimited strength files I end up with :
>
> Tests in error:
>
> // probably caused by the fact I have'built from the trunk but using
> jboss600 ?
>
>
> testMessagingClient(org.jboss.test.ws.jaxws.samples.jmstransport.FromJavaJMSTransportTestCase)
>
> testMessagingClient(org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase)
>
> testJMSEndpointPort(org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase)
>
> testHTTPEndpointPort(org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase)
yes, if you're using jboss600 profile in the jbossws testsuite, but
running against AS trunk, that might be the reason..
> // is is excluded actually ?
> test(org.jboss.test.ws.jaxws.samples.wssePolicy.UsernameTestCase)
>
> testWrongPassword(org.jboss.test.ws.jaxws.samples.wssePolicy.UsernameTestCase)
Yes, it should be, given it requires SSL connector to be setup on AS
(jbossweb configuration), which is not the case by default.
> // the only one which fails
>
> testServletClient(org.jboss.test.ws.jaxws.cxf.webserviceref.WebServiceRefServletTestCase)
>
> which looks like is caused by
>
> 23:18:30,874 ERROR
> [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jaxws-cxf-webserviceref-servlet-client].[ServletClient]]
> Allocate exception for servlet ServletClient:
> java.lang.NoClassDefFoundError: org/jboss/virtual/VFS
> at
> org.springframework.core.io.AbstractFileResolvingResource$VfsResourceDelegate.getResource(AbstractFileResolvingResource.java:92)
> [:3.0.1.RELEASE]
>
> strange error :-)
Again, an exclusion issue I think; I've excluded that test recently as
there's a bug in the jboss-spring integration with the latest JBoss AS
versions (which use new version of jboss-vfs). See JBWS-3039.
> do you see the same picture ?
>
> By the way what is right way to run framework tests ? Also
> -Ptestsuite,jboss600 directly from testsuite/framework-tests ? As it
> looks like they are not picked up when running then directly from
> jbosscxf/ root. I just seeing a lot of framework tests failing
You should be running from jbossws-cxf root for a proper consideration
of exclusions; if you have failures in the cxf-tests group, the
framework tests group is not run, unless you also provide the -Phudson
profile (so something like "mvn -Ptestsuite,hudson,jboss600 test).
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
16 years
Re: [jbossws-dev] CXF 2.2.9
by Alessio Soldano
Hi Sergey,
CC-ing the dev list, as this can be of public interest
Sergey Beryozkin wrote:
> Hi Alessio
>
> I was quite 'slow' yesterday when you kind of suggested to open a
> JBoss JIRA to do with migrating to 2.2.9, see, I had a long break :-).
> Realized it when saw you working today (on the bank holiday :-)).
>
> Just tried to run JBossWS/CXF tests with CXF 2.2.9.
I've done a fast check of this yesterday night too, I currently see 5
failures against AS 6.0.0.M3. Didn't use AS trunk for this check as it's
not in a really good shape at the moment, see the failures in AS601 jobs
at http://jbossws.jboss.org:8180/hudson/
> Interesting, when running -Ptestsuite,jboss601 I see :
>
> "[INFO] Building JBoss Web Services - Stack CXF Testsuite
> [INFO] task-segment: [test]
> [INFO]
> ------------------------------------------------------------------------
> Downloading:
> http://repo1.maven.org/maven2/org/jboss/spec/jboss-javaee6-specs-bom/1.0....
> [INFO] Unable to find resource
> 'org.jboss.spec:jboss-javaee6-specs-bom:pom:1.0.0.Beta1' in repository
> central (http://repo1.maven.org/maven2)
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error building POM (may not be this project's POM).
>
>
> Project ID: org.jboss.spec:jboss-javaee6-specs-bom
>
> Reason: POM 'org.jboss.spec:jboss-javaee6-specs-bom' not found in
> repository: Unable to download the artifact from any repository
> "
Do you have the jboss repository properly configured in your maven
settings? Is this still outstanding? I need to verify in any case.
Btw, on a related topic, yesterday I saw a thread on the AS dev list
(jboss-development(a)lists.jboss.org) started by Paul Gier ([jboss-dev]
Nexus configuration changes, 2nd June) talking about updates on the
jboss m2 repository configuration, you might want to check that too.
>
> But this error does not exist when doing -Ptestsuite,jboss600 - not
> sure why.
Different dependencies on AS 6 M3. The container related dependencies
depends on the container selected through jbossXYZ profile.
> Anyway, when running with jboss600 I see :
>
> Tests in error:
>
> testMessagingClient(org.jboss.test.ws.jaxws.samples.jmstransport.FromJavaJMSTransportTestCase)
>
> testMessagingClient(org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase)
>
> testJMSEndpointPort(org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase)
>
> testHTTPEndpointPort(org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase)
> test(org.jboss.test.ws.jaxws.samples.wssePolicy.UsernameTestCase)
>
> testWrongPassword(org.jboss.test.ws.jaxws.samples.wssePolicy.UsernameTestCase)
>
> testScenario2(org.jboss.test.ws.jaxws.cxf.interop.wstrust10.SymmetricBindingClientTestCase)
>
> testScenario5(org.jboss.test.ws.jaxws.cxf.interop.wstrust10.SymmetricBindingClientTestCase)
>
> testScenario6(org.jboss.test.ws.jaxws.cxf.interop.wstrust10.SymmetricBindingClientTestCase)
>
> testServletClient(org.jboss.test.ws.jaxws.cxf.webserviceref.WebServiceRefServletTestCase)
>
> testScenario9(org.jboss.test.ws.jaxws.cxf.interop.wstrust10.AsymmetricBindingClientTestCase)
>
> testScenario10(org.jboss.test.ws.jaxws.cxf.interop.wstrust10.AsymmetricBindingClientTestCase)
>
> Tests run: 42, Failures: 0, Errors: 12, Skipped: 0
>
> WSTrust related tests fail with :
> "Caused by: java.io.IOException: exception unwrapping private key -
> java.security.InvalidKeyException: Illegal key size
> at
> org.bouncycastle.jce.provider.JDKPKCS12KeyStore.unwrapKey(Unknown Source)
> at
> org.bouncycastle.jce.provider.JDKPKCS12KeyStore.engineLoad(Unknown Source)
> at java.security.KeyStore.load(KeyStore.java:1185)
> at
> org.apache.ws.security.components.crypto.AbstractCrypto.load(AbstractCrypto.java:168)
> "
>
> I'm thinking do I have to update my OS/environment somehow ?
Yes, as you already said in the other email, you need the JCE unlimited
strength file for passing some of the security tests. Not sure about the
other tests, but you might want to start by issuing a "mvn -Ptestsuite
clean" when you change from using a container to using another one. That
way you're sure all the tests are cleaned and the excludes re-considered.
Btw, I currently see these 5 failures against AS6 M3:
Tests in error:
testTarget(org.jboss.test.ws.jaxws.smoke.tools.WSConsumerTestCase)
testAdditionalHeaders(org.jboss.test.ws.jaxws.smoke.tools.WSConsumerTestCase)
testAddItem(org.jboss.test.ws.jaxws.samples.addressing.AddressingStatefulTestCase)
testGetItems(org.jboss.test.ws.jaxws.samples.addressing.AddressingStatefulTestCase)
testCheckout(org.jboss.test.ws.jaxws.samples.addressing.AddressingStatefulTestCase)
The WSConsumerTestCase ones are somehow related to CXF tools generating
jaxws 2.2 stuff even when the 2.1 target is specified, I need to check
if this is a problem in our integration or not.
I still need to analyse the AddressingStatefulTestCase failures instead.
> JMS related ones are caused by :
> DEPLOYMENTS IN ERROR:
> Deployment
> "vfs:///home/sberyozkin/work/jboss/jboss-cxf/modules/testsuite/cxf-tests/target/test-libs/jaxws-fromjava-jmstransport-as6.sar"
> is in error due to the following reason(s):
> javax.naming.NameNotFoundException: RequestQueue not bound
>
> Note, I haven't rebuild the trunk in a while, can that be the cause ?
Maybe... but above I read you've used jboss600 profile, don't you?
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
16 years