Bug 1170711

Summary: JBossWS testsuite failure of WSSecurityPolicyExamples21xTestCase on IBM JDK7 with NIO webconnector
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Jan Blizňák <jbliznak>
Component: Web ServicesAssignee: Alessio Soldano <asoldano>
Status: CLOSED CANTFIX QA Contact: Rostislav Svoboda <rsvoboda>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.1   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-24 11:38:20 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:

Description Jan Blizňák 2014-12-04 16:28:12 UTC
Test failure occurs when running server on IBM JDK7 with NIO web connector. During setup of the testcase new HTTPS connector is being added which is where the exception is thrown.

Failed

org.jboss.wsf.test.JBossWSCXFTestSetup.org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples21xTestCase (from org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples21xTestCase)

Error Message

{"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"JBAS014671: Failed services" => {"jboss.web.connector.jbws-test-https-connector" => "org.jboss.msc.service.StartException in service jboss.web.connector.jbws-test-https-connector: JBAS018007: Error starting web connector     Caused by: LifecycleException:  JBWEB000023: Protocol handler initialization failed"}}}}
Stacktrace

java.lang.Exception: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"JBAS014671: Failed services" => {"jboss.web.connector.jbws-test-https-connector" => "org.jboss.msc.service.StartException in service jboss.web.connector.jbws-test-https-connector: JBAS018007: Error starting web connector
    Caused by: LifecycleException:  JBWEB000023: Protocol handler initialization failed"}}}}
	at org.jboss.as.webservices.deployer.RemoteDeployer.checkResult(RemoteDeployer.java:325)
	at org.jboss.as.webservices.deployer.RemoteDeployer.applyUpdate(RemoteDeployer.java:312)
	at org.jboss.as.webservices.deployer.RemoteDeployer.addHttpsConnector(RemoteDeployer.java:285)
	at org.jboss.wsf.test.JBossWSTestHelper.addHttpsConnector(JBossWSTestHelper.java:402)
	at org.jboss.wsf.test.JBossWSTestSetup.setUp(JBossWSTestSetup.java:219)
	at org.jboss.wsf.test.JBossWSCXFTestSetup.setUp(JBossWSCXFTestSetup.java:72)
	at org.jboss.wsf.test.JBossWSTestSetup$1.protect(JBossWSTestSetup.java:140)
	at junit.framework.TestResult.runProtected(TestResult.java:128)
	at org.jboss.wsf.test.JBossWSTestSetup.run(JBossWSTestSetup.java:148)
	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:94)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
	at java.lang.reflect.Method.invoke(Method.java:619)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)


How reproducible:
always

Steps to Reproduce:
1. run testsuite

Additional info:
This failure would have been spotted much earlier, but until recently, we weren't able to set https connector dynamically added/removed during test execution to use org.apache.coyote.http11.Http11NioProtocol

Comment 1 Jan Blizňák 2014-12-04 16:30:38 UTC
Actually this seems to be a known issue.

Comment 2 Jan Blizňák 2015-03-18 16:38:41 UTC
The same issue is with IBM JDK8.