Created attachment 945096 [details] Productization patch for JBossWS sources Description of problem: Running JBossWS testsuite I got unexpected failures of testcases using custom HTTPS connector which is added/removed as needed. Version-Release number of selected component (if applicable): EAP 6.4.0.DR4, JBossWS 4.3.1.Final (productized patch applied), JDK 1.7.0_67 with installed JCE Unlimited Strength Jurisdiction Policy Files + BouncyCastle 1.51 How reproducible: always Steps to Reproduce: 1. checkout JBossWS project ($TS) svn co http://anonsvn.jboss.org/repos/jbossws/stack/cxf/tags/jbossws-cxf-4.3.1.Final 2. apply productization patch: (cd $TS; patch -p0 < $PATCH_FOR_DR4) 3. extract top level dir of EAP maven repo ($EAP_REPO) - so that dirs exist $EAP_REPO/org, $EAP_REPO/com etc. 4. extract EAP ($EAP_HOME) 5. start EAP (on background/another terminal) 6. copy endorsed libraries: cp $EAP_HOME/modules/system/layers/base/org/jboss/ws/cxf/jbossws-cxf-factories/main/jbossws-cxf-factories-4.3.1.Final.jar $TS/modules/endorsed/target/ 7. run testsuite: mvn -Dmaven.repo.local=$EAP_REPO -Djbossws.integration.target=jboss720 -Djboss720.home=$EAP_HOME -Djboss.bind.address=localhost -Ptestsuite,hudson,jboss720 clean integration-test (your ~/.m2/settings.xml must define repository http://repository.jboss.org/nexus/content/groups/public/ or add custom settings.xml to the command above) 7a. you don't have to run whole testsuite, add -Dtest=xxx property to the command above, where xxx is for example WSSecurityPolicyExamples21xTestCase, WSTrustBearerTestCase, WSSecurityPolicyExamples23xTestCase To repeat you need to start with fresh EAP, so start at least with step 4. Actual results: with 6.4.0.DR4 some testcases where custom HTTPS connector is added failed with: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014749: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.web.connector.jbws-test-https-connector is already registered"}} Expected results: with 6.4.0.DR3 and earlier they don't fail with this issue
The connector can't be added because it really exists in EAP. It seems that the behaviour has changed in 6.4.0.DR4: /subsystem=web/connector=abcd:remove now requires reload, so new one with same name can't be added until reload
Jan, I've cut a new release of the org.jboss.ws:jbossws-jboss720-tests-integration artifact (4.3.1.Final), including a fix for allowing resource service restart when removing the https connector in RemoteDeployer. Please update your productization patch to have the following line in the stack main pom.xml: <jbossws.jboss720.version>4.3.1.Final</jbossws.jboss720.version>
Moving to ON_QA, BZ 1153972 is VERIFIED.
Verified on 6.4.0.DR10