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

Bug 1092410

Summary: WSI BSP 1.1 tests are failing on JDK 7 when NIO web connector is used
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Rostislav Svoboda <rsvoboda>
Component: Web ServicesAssignee: Jim Ma <ema>
Status: CLOSED EOL QA Contact: Rostislav Svoboda <rsvoboda>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: asoldano, jbliznak
Target Milestone: ---   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:45:55 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
WSI_Test_Java_WGD_BSP_1.1.zip none

Description Rostislav Svoboda 2014-04-29 09:12:47 UTC
Failed tests from org.jboss.test.ws.jaxws.samples.wsse.policy.oasis:
  WSSecurityPolicyExamples22xTestCase.test224
  WSSecurityPolicyExamples23xTestCase.test2324

Sometimes I see 3 failures, sometimes just one. It's kind of random, but definitely problematic on JDK 7. WSI BP 1.2 and 2.0 are fine on JDK 7.

Tested on:
  http://station5.brq.redhat.com:8180/job/wsi-bsp-11-jdk7/ (RHEL 6)
  my local machine (F 19)

Tested on Oracle JDK with unlimited crypto ++ BC
  jdk1.7.0_51
  jdk1.7.0_25

Error stack trace:
Caused by: org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader.
	at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:84)
	at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:51)
	at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:40)
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
	at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:113)
	at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69)
	at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34)
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
	at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:835)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1614)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1504)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1310)
	at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
	at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:628)
	at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
	at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:565)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:474)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:377)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:330)
	at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
	at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)

Comment 1 Rostislav Svoboda 2014-04-30 09:22:57 UTC
Server log contains message:
....
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ':' (code 58) excepted space, or '>' or "/>"
 at [row,col {unknown-source}]: [1,163]
	at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:639)
	at com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java:2994)
	at com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:2961)
	at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2837)
	at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1072)
	at org.apache.cxf.staxutils.DepthXMLStreamReader.next(DepthXMLStreamReader.java:220) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1]
	at org.apache.cxf.staxutils.PartialXMLStreamReader.next(PartialXMLStreamReader.java:46) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1]
	at org.apache.cxf.staxutils.StaxUtils.copy(StaxUtils.java:764) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1]
	at org.apache.cxf.staxutils.StaxUtils.copy(StaxUtils.java:694) [cxf-api-2.7.10.redhat-1.jar:2.7.10.redhat-1]
	at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:170)

Comment 2 Rostislav Svoboda 2014-04-30 13:59:46 UTC
When running only  WSSecurityPolicyExamples23xTestCase.test2324 no failure present. Executed 30 times, no 'Error reading XMLStreamReader' failure.

So the tests in WSSecurityPolicyExamples23xTestCase must influence each other. Better isolation would be probably required. Reset the bus ?

Comment 3 Jim Ma 2014-05-04 10:54:49 UTC
I managed to reproduce this issue locally for some time today and no luck. Can you please help disable the surefire parallel mode to see if this help?

Comment 4 Rostislav Svoboda 2014-05-07 08:48:26 UTC
Disabling surefire parallel mode didn't help.

Comment 5 Rostislav Svoboda 2014-05-07 09:51:48 UTC
Running again with EAP 6.3.0 ER3 showed that failures are gone.

6 runs on Jenkins + 15 runs on local machine, no failure.

Trying to findout what fixed this problem

Comment 6 Rostislav Svoboda 2014-05-07 11:21:13 UTC
Upgrade of JBossWeb helped to suppress the issue - I tried ER2 + JBossWeb from ER3.

JBossWeb from ER3 changed implementation of web connector used on JDK 7.
JIO connector is used as default for both JDK 6 and 7. See BZ 1091849 for details.

I reconfigured web connector to use NIO and issue appeared again.
<connector name="http" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="http" socket-binding="http"/>

So in default configuration issue is not present but with use of NIO connector it's back.

Comment 7 Rostislav Svoboda 2014-05-07 11:44:20 UTC
Steps to reproduce on EAP 6.3.0 ER3:

1) Download http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.3.0.ER3/jboss-eap-6.3.0.ER3.zip and http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.3.0.ER3/jboss-eap-6.3.0.ER3-maven-repository.zip ++ unzip it
2) prepare settings-630er3.xml file - similar to http://pastebin.test.redhat.com/207547
3) checkout https://anonsvn.jboss.org/repos/jbossws/projects/wsi-bp-test/branches/wsi-bp-test-4.3.0.Beta2
4) configure server to use NIO -- <connector name="http" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="http" socket-binding="http"/>
5) run server with JDK 7 ++ BC ++ unlimited crypto
6) run sh monitor.sh -config monitor-config-bsp11.xml from WSI_Test_Java_WGD_BSP_1.1
7) run tests from bsp11-tests module with with JDK 7 ++ BC ++ unlimited crypto -- mvn -s /home/rsvoboda/TESTING/630ER3/settings-630er3.xml -Dmaven.repo.local=/home/rsvoboda/TESTING/630ER3/local-repo -Dlog4j.output.dir=target -Djboss.home=/home/rsvoboda/TESTING/630ER3/jboss-eap-6.3 -Pjboss720,use-eap6-bom -Dversion.eap6-supported-artifacts=6.3.0.Beta1 -Djboss720.version=7.4.0.Final-redhat-11 -Dno-slf4j-log4j12 clean integration-test
8) check server log

Comment 8 Rostislav Svoboda 2014-07-25 14:00:05 UTC
Checked on EAP 6.3.0 ER10 and issue is still present.

Comment 9 Rostislav Svoboda 2014-07-25 14:00:50 UTC
Created attachment 920993 [details]
WSI_Test_Java_WGD_BSP_1.1.zip

Comment 10 Jim Ma 2014-11-06 07:04:33 UTC
Except this test sends message to a proxy to log the request/response message, there is no difference from the same test in jbossws test suite.Given these tests passed with JIO connector, I think it's possible there is some minor issue still in jbossweb's nio connector.Can we get Remy to have a look at this please ?

Comment 11 Rostislav Svoboda 2014-11-13 16:39:17 UTC
Checked EAP 6.4.0 DR9 and had failure in test224 from WSSecurityPolicyExamples22xTestCase.

Caused by: org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader.

Issue is still present.

Comment 13 Jan Blizňák 2015-11-28 23:47:35 UTC
Issue still present with 6.4.5.CP.CR3

Comment 14 Jan Blizňák 2016-03-31 11:29:20 UTC
Issue is still present with 6.4.7.CP.CR3