Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 901119 (JBPAPP6-1171)

Summary: JBossWS CXF 4.0.4.GA TS stuck when running against 6.0.1 ER3
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Rostislav Svoboda <rsvoboda>
Component: Documentation, RemotingAssignee: Jimmy Wilson <jawilson>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.0.0CC: asoldano, atangrin, cfang, david.lloyd, fnasser, jawilson, rsvoboda
Target Milestone: ---   
Target Release: EAP 6.0.1   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-1171
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-16 08:13:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
surefire-stacktrace.txt
none
launcher-stacktrace.txt
none
server-stacktrace.txt
none
settings-ws-backward-compatibility.xml none

Description Rostislav Svoboda 2012-10-29 11:43:46 UTC
Affects: Release Notes
project_key: JBPAPP6

I'm using JBossWS CXF TS 4.0.4.GA && latest EAP 6.x release to check backward compatibility for clients.

I have problem with EAP 6.0.1 ER3, TS is stuck and doesn't continue with execution, 
It's working when running against EAP 6.0.1 ER2, tested on RHEL 6 and locally on Fedora 17.

Thread dumps attached. 

JOB - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-6x-jbossws-backward-compatibility/
RUNS - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-6x-jbossws-backward-compatibility/4/consoleText and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-6x-jbossws-backward-compatibility/5/consoleText

Executions ends on org.jboss.test.ws.jaxws.samples.advanced.retail.RetailSampleTestCase, on my local machine it's stuck on org.jboss.test.ws.jaxws.complex.ComplexTestCase. Tests are not executed in the same order even on jenkins, but it's stuck on the same testcase, see job page and Test Result Trend chart.

There can be incompatibility in testsuite or this can indicate problem on server side. I can't say which case it is for sure, I'm working on deeper investigation. Please take a look at it too.


Steps to reproduce:
 - get prepared WS TS - http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-jbossws-testsuite-prepare/24/artifact/stack-cxf.zip
 - get maven repo zip for 6.0.0.GA - http://download.devel.redhat.com/released/JBEAP-6/6.0.0/zip/jboss-eap-6.0.0-maven-repository.zip
 - get EAP 6.0.1.ER3 - http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.0.1-ER3/jboss-eap-6.0.1.ER3.zip

 - unzip maven repo zip for 6.0.0.GA 
 - prepare settings.xml for testing (example attached) which is using unzipped repo

 - unzip and run EAP 6.0.1 ER3
 - define JBOSS_INSTANCE - path to unzipped EAP 
 - define NATIVE_CORE_NAME - `basename $JBOSS_INSTANCE/modules/org/jboss/ws/native/jbossws-native-core/main/jbossws-native-core-*.jar`
 - unzip prepared WS TS
 - define LOCAL_REPO - where all artifacts will be downloaded
 - define SETTINGS_FILE - path to prepared settings file
 - enter modules/testsuite
 - execute 
{code}
mvn -e -s $SETTINGS_FILE -Ptestsuite,hudson,jboss712 -Dmaven.repo.local=$LOCAL_REPO -Djboss712.home=$JBOSS_INSTANCE -Djbossws-native-core.filename=$NATIVE_CORE_NAME clean integration-test 
{code}

component upgrades ER2 -> ER3:
{code}
 - apache abdera              1.1.2          -> 1.1.3
 - apache cxf                 2.4.8-patch-01 -> 2.4.9
 - apache neethi              3.0.1          -> 3.0.2
 - apache ws security         1.6.6          -> 1.6.7
 - freemarker                 2.3.18         -> 2.3.19
 - hornetq                    2.2.19.Final   -> 2.2.22.Final
 - infinispan                 5.1.7.Final    -> 5.1.8.Final
 - jboss as console           1.4.0.Final    -> 1.4.2.Final
 - jboss ironjacamar          1.0.12.Final   -> 1.0.13.Final
 - jboss mod_cluster          1.2.2.Final    -> 1.2.3.Final
 - jboss remoting3            3.2.8.SP1      -> 3.2.12.GA
 - jboss spec jsf 2.1         2.0.4.Final    -> 2.0.7.Final
 - jboss transactions         4.16.4.Final   -> 4.16.6.Final
 - jboss weld                 1.1.9.Final    -> 1.1.10.Final
 - jboss ws common tools      1.0.1.GA       -> 1.0.2.GA
 - jboss ws cxf               4.0.5.GA       -> 4.0.6.GA
 - jboss ws native            4.0.5.GA       -> 4.0.6.GA
 - jboss ws shared testsuite  4.0.3.GA       -> 4.0.7.GA
 - jboss xnio                 3.0.6.GA       -> 3.0.7.GA
 - picketbox                  4.0.13.Final   -> 4.0.14.Final
 - sun jsf impl               2.1.11         -> 2.1.13
{code}

Comment 1 Rostislav Svoboda 2012-10-29 11:46:22 UTC
4673 org.codehaus.plexus.classworlds.launcher.Launcher
5266 /home/rsvoboda/TESTING/BACKWARD/stack-cxf/modules/testsuite/shared-tests/target/surefire/surefirebooter319490176128857553.jar
4582 /home/rsvoboda/TESTING/BACKWARD/jboss-eap-6.0/jboss-modules.jar



rsvoboda  4673  2.1  8.2 3401996 666564 pts/2  Sl+  11:57   0:40 /opt/jdk/bin/java -Xms128m -Xmx1303m -XX:MaxPermSize=256m -classpath /opt/maven/boot/plexus-classworlds-2.4.jar -Dclassworlds.conf=/opt/maven/bin/m2.conf -Dmaven.home=/opt/maven org.codehaus.plexus.classworlds.launcher.Launcher -e -s /home/rsvoboda/TESTING/BACKWARD/settings-ws-backward-compatibility.xml -Ptestsuite,hudson,jboss712 -Dmaven.repo.local=/home/rsvoboda/TESTING/BACKWARD/local-repo -Djboss712.home=/home/rsvoboda/TESTING/BACKWARD/jboss-eap-6.0 -Djbossws-native-core.filename=jbossws-native-core-4.0.6.GA-redhat-1.jar clean integration-test

rsvoboda  5266  1.0  1.9 3572800 155572 pts/2  Sl+  11:59   0:18 /opt/jdk1.6.0_31/jre/bin/java -Djava.security.manager -Djava.security.policy=src/test/etc/tst.policy -Xmx768m -XX:MaxPermSize=450m -Djbossws.deployer.authentication.username=admin -Djbossws.deployer.authentication.password=admin -Djava.endorsed.dirs=/home/rsvoboda/TESTING/BACKWARD/stack-cxf/modules/testsuite/shared-tests/target/endorsed -jar /home/rsvoboda/TESTING/BACKWARD/stack-cxf/modules/testsuite/shared-tests/target/surefire/surefirebooter319490176128857553.jar /home/rsvoboda/TESTING/BACKWARD/stack-cxf/modules/testsuite/shared-tests/target/surefire/surefire4111486471850983991tmp /home/rsvoboda/TESTING/BACKWARD/stack-cxf/modules/testsuite/shared-tests/target/surefire/surefire741771785837663982tmp

rsvoboda  4582  2.3  7.8 4002788 636052 pts/4  Sl+  11:57   0:44 /opt/jdk/bin/java -D[Standalone] -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml -Dorg.jboss.boot.log.file=/home/rsvoboda/TESTING/BACKWARD/jboss-eap-6.0/standalone/log/boot.log -Dlogging.configuration=file:/home/rsvoboda/TESTING/BACKWARD/jboss-eap-6.0/standalone/configuration/logging.properties -jar /home/rsvoboda/TESTING/BACKWARD/jboss-eap-6.0/jboss-modules.jar -mp /home/rsvoboda/TESTING/BACKWARD/jboss-eap-6.0/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/home/rsvoboda/TESTING/BACKWARD/jboss-eap-6.0 -Djboss.server.base.dir=/home/rsvoboda/TESTING/BACKWARD/jboss-eap-6.0/standalone


Comment 2 Rostislav Svoboda 2012-10-29 11:46:22 UTC
Attachment: Added: surefire-stacktrace.txt
Attachment: Added: launcher-stacktrace.txt
Attachment: Added: server-stacktrace.txt


Comment 3 Rostislav Svoboda 2012-10-29 11:47:34 UTC
Attachment: Added: settings-ws-backward-compatibility.xml


Comment 4 Rostislav Svoboda 2012-10-29 13:01:09 UTC
Moving to critical, with old remoting in EAP TS works, I guess we have backward compatibility issue with JBoss Remoting. 

I tweaked server side - using ER2 based jboss-remoting-3.2.8.SP1-redhat-1.jar instead of ER3 based jboss-remoting-3.2.12.GA-redhat-1.jar.

TS is NOT stuck, ends as expected + 2 errors.

testWebService(org.jboss.test.ws.jaxws.jbws1611.JBWS1611TestCase): The given SOAPAction uri:placeBuyOrder does not match an operation.
testServletClient(org.jboss.test.ws.jaxws.samples.webservicerefsec.WebServiceRefSecTestCase): Server returned HTTP response code: 500 for URL: http://localhost:8080/jaxws-samples-webservicerefsec-servlet-client?echo=HelloWorld


Comment 5 Fernando Nasser 2012-10-30 19:02:02 UTC
Reassigning as it is Remoting 3

Comment 6 David M. Lloyd 2012-10-30 19:10:46 UTC
The only way to get around this is to apply the new XNIO and Remoting versions to the ER2 side.  This problem is due to a bug in Remoting dealing with connection termination; the fix in .11/.12 brings out the problem much more frequently in .8 and it can't be helped.  Note that the problem can still occur between two .8 versions of Remoting.

Comment 7 Fernando Nasser 2012-10-30 19:16:30 UTC
Nothing can be done about this one, and the ER2 version of remoting has not been shipped anywhere.

Comment 8 Rostislav Svoboda 2012-10-31 08:08:10 UTC
EAP 6.0.0.GA contains org.jboss.remoting3:jboss-remoting:jar:3.2.8.GA-redhat-1.
I use JBossWS CXF 4.0.4.GA TS to check WS backward compatibility on client side, this TS is configured to use jboss-remoting from EAP 6.0.0.GA - that means 3.2.8.GA-redhat-1.

Regarding to your comment it seems to me that customers who will update server to EAP 6.0.1.GA will have to update client dependencies too.

Do you agree with me? Is there another solution?

If client libraries must be updated it will mean backward compatibility issue and it must be documented at least for RN.


Comment 10 Misty Stanley-Jones 2012-11-05 04:41:01 UTC
Release Notes Docs Status: Added: Not Required


Comment 11 Fernando Nasser 2012-11-06 15:54:02 UTC
Release notes text will be provided by Jimmy

Comment 12 Fernando Nasser 2012-11-06 15:54:02 UTC
Affects: Added: Release Notes


Comment 14 Fernando Nasser 2012-11-07 14:31:32 UTC
Jimmy, was 3.2.11.GA when the fix frst went in?

Comment 15 Anne-Louise Tangring 2012-11-13 20:43:47 UTC
Release Notes Docs Status: Removed: Not Required 
Docs QE Status: Removed: NEW 


Comment 17 Jimmy Wilson 2012-11-16 07:36:21 UTC
See JBPAPP6-1064's comment for the release notes related to the underlying issue at work here.  JBPAPP6-1064 needs to be documented rather than this downstream effect.

Comment 18 Rostislav Svoboda 2012-11-16 08:13:00 UTC
Closing, JBPAPP6-1064 was reopened to check RN text in ER4.

Comment 19 Rostislav Svoboda 2012-12-19 12:36:39 UTC
Link: Added: This issue is related to JBPAPP6-1064