Bug 1016484 - FSW 6.0.0 ER4 quickstarts/switchyard/demos/policy-security-wss-signencrypt
Summary: FSW 6.0.0 ER4 quickstarts/switchyard/demos/policy-security-wss-signencrypt
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Examples, RT Governance
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 6.1.0
Assignee: Matej Melko
QA Contact: ppecka
URL:
Whiteboard:
: 1018889 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-08 09:02 UTC by ppecka
Modified: 2021-11-08 10:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The policy-security-wss-signencrypt will not run if the RTGov client and server are both installed. It will work if you install Red Hat JBoss Fuse Service Works with the RTGov client only or install it with both the RTGov client and server, then undeploy all of the WAR files in the deployments/overlord-rtgov directory.
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description ppecka 2013-10-08 09:02:25 UTC
Description of problem:
I have no success running policy-security-wss-signencrypt quickstart, by following Readme file instructions. 
Step where quickstart should succeed with test fails
mvn exec:java -Dexec.args="confidentiality signencrypt" -Djavax.net.ssl.trustStore=connector.jk

[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Quickstart Demo : Security Policy : WSS Signature+Encryption (+SSL) 1.1.0.M3-redhat-2
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1-redhat-1:java (default-cli) @ switchyard-quickstart-demo-policy-security-wss-signencrypt >>>
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-java-version) @ switchyard-quickstart-demo-policy-security-wss-signencrypt ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-maven-version) @ switchyard-quickstart-demo-policy-security-wss-signencrypt ---
[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1-redhat-1:java (default-cli) @ switchyard-quickstart-demo-policy-security-wss-signencrypt <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1-redhat-1:java (default-cli) @ switchyard-quickstart-demo-policy-security-wss-signencrypt ---
11:04:05,876 INFO  [org.switchyard.quickstarts.demo.policy.security.wss.signencrypt.WorkServiceMain] Invoking work service at endpoint: https://localhost:8443/policy-security-wss-signencrypt/WorkService
[WARNING] 
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
	at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.Exception: Error invoking work service (check server log)
	at org.switchyard.quickstarts.demo.policy.security.wss.signencrypt.WorkServiceMain.invokeWorkService(WorkServiceMain.java:56)
	at org.switchyard.quickstarts.demo.policy.security.wss.signencrypt.WorkServiceMain.main(WorkServiceMain.java:95)
	... 6 more
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.252s
[INFO] Finished at: Tue Oct 08 11:04:06 CEST 2013
[INFO] Final Memory: 51M/591M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1-redhat-1:java (default-cli) on project switchyard-quickstart-demo-policy-security-wss-signencrypt: An exception occured while executing the Java class. null: InvocationTargetException: Error invoking work service (check server log) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException


Version-Release number of selected component (if applicable):
soa-6.0.0-ER4


Steps to Reproduce:
1.
2.
3.

Actual results:
10:37:03,425 WARNING [org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor] (http-/127.0.0.1:8443-1) : org.apache.ws.security.WSSecurityException: General security error (Unable to load class org.apache.ws.security.processor.SignatureProcessor)
	at org.apache.ws.security.WSSConfig.getProcessor(WSSConfig.java:789) [wss4j-1.6.9-redhat-2.jar:1.6.9-redhat-2]
	at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:394) [wss4j-1.6.9-redhat-2.jar:1.6.9-redhat-2]
	at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:277) [cxf-rt-ws-security-2.6.6-redhat-3.jar:2.6.6-redhat-3]
	at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:96) [cxf-rt-ws-security-2.6.6-redhat-3.jar:2.6.6-redhat-3]
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262) [cxf-api-2.6.6-redhat-3.jar:2.6.6-redhat-3]
	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-api-2.6.6-redhat-3.jar:2.6.6-redhat-3]
	at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:237) [cxf-rt-transports-http-2.6.6-redhat-3.jar:2.6.6-redhat-3]
	at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:95) [jbossws-cxf-server-4.1.3.Final-redhat-3.jar:4.1.3.Final-redhat-3]
	at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156) [jbossws-cxf-server-4.1.3.Final-redhat-3.jar:4.1.3.Final-redhat-3]
	at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87) [jbossws-cxf-server-4.1.3.Final-redhat-3.jar:4.1.3.Final-redhat-3]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:225) [cxf-rt-transports-http-2.6.6-redhat-3.jar:2.6.6-redhat-3]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:145) [cxf-rt-transports-http-2.6.6-redhat-3.jar:2.6.6-redhat-3]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
	at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135) [jbossws-cxf-server-4.1.3.Final-redhat-3.jar:4.1.3.Final-redhat-3]
	at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920)
	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
Caused by: java.lang.ClassCastException: org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignatureFactory cannot be cast to javax.xml.crypto.dsig.XMLSignatureFactory
	at javax.xml.crypto.dsig.XMLSignatureFactory.getInstance(XMLSignatureFactory.java:290) [rt.jar:1.7.0_21]
	at org.apache.ws.security.processor.SignatureProcessor.<init>(SignatureProcessor.java:98) [wss4j-1.6.9-redhat-2.jar:1.6.9-redhat-2]
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_21]
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_21]
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_21]
	at java.lang.reflect.Constructor.newInstance(Constructor.java:525) [rt.jar:1.7.0_21]
	at java.lang.Class.newInstance0(Class.java:374) [rt.jar:1.7.0_21]
	at java.lang.Class.newInstance(Class.java:327) [rt.jar:1.7.0_21]
	at org.apache.ws.security.WSSConfig.getProcessor(WSSConfig.java:784) [wss4j-1.6.9-redhat-2.jar:1.6.9-redhat-2]
	... 27 more


Expected results:


Additional info:
I also took similar steps to https://issues.jboss.org/browse/SWITCHYARD-1646?focusedCommentId=12802632&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12802632

Comment 1 Martin Vecera 2013-10-14 15:42:59 UTC
*** Bug 1018889 has been marked as a duplicate of this bug. ***

Comment 2 Keith Babo 2013-10-15 17:59:10 UTC
I have not been able to pinpoint the exact cause, but this appears to be introduced by the installation of RTGov server components.  This quickstart passes for me in the following scenarios:

1) Install FSW ER4 with RTGov client only.
2) Install FSW ER4 with RTGov client+server, then undeploy all wars in the deployments/overlord-rtgov directory.

The quickstart fails for me on a fresh install with RTGov client+server (the default).

Comment 4 Aileen 2015-03-06 10:41:43 UTC
There is an issue in SY that needs investigating when you come to do the RTGov productisation, to identify what is causing the corruption within the SY server.


Note You need to log in before you can comment on or make changes to this bug.