You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jan Bernhardt (Created) (JIRA)" <ji...@apache.org> on 2011/12/05 17:30:39 UTC
[jira] [Created] (CXF-3954) Could not obtain STS metadata. MEX call
failed
Could not obtain STS metadata. MEX call failed
----------------------------------------------
Key: CXF-3954
URL: https://issues.apache.org/jira/browse/CXF-3954
Project: CXF
Issue Type: Bug
Components: Services
Affects Versions: 2.5
Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: /opt/maven
Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
Java home: /usr/java/jdk1.6.0_25/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-71.el6.x86_64", arch: "amd64", family: "unix"
Reporter: Jan Bernhardt
I tried to deploy a cxf consumer as part of a servlet webapplication. When I run my example using mvn jetty:run everything works just fine as expected. But when I deploy my application to my glassfish 3 container I get the following error message:
com.sun.xml.ws.api.security.trust.WSTrustException: WST0017:Could not obtain STS metadata. MEX call to STS http://my.server.org:8081/SecurityTokenService/UT/mex failed.
Looking into the STS Server Log it contains the following errors:
[#|2011-12-05T17:28:46.222+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=20;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
org.apache.cxf.binding.soap.SoapFault: A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint.
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:144)
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:123)
[#|2011-12-05T17:28:46.235+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=19;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown.
at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60)
at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3954) Could not obtain STS metadata. MEX call
failed
Posted by "Jan Bernhardt (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Bernhardt updated CXF-3954:
-------------------------------
Comment: was deleted
(was: Just an insufficient setup, not an cxf bug.)
> Could not obtain STS metadata. MEX call failed
> ----------------------------------------------
>
> Key: CXF-3954
> URL: https://issues.apache.org/jira/browse/CXF-3954
> Project: CXF
> Issue Type: Bug
> Components: Services
> Affects Versions: 2.5
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: /opt/maven
> Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
> Java home: /usr/java/jdk1.6.0_25/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-71.el6.x86_64", arch: "amd64", family: "unix"
> Reporter: Jan Bernhardt
> Labels: mex, securitytokenservice, sts, sts-client
>
> I tried to deploy a cxf consumer as part of a servlet webapplication. When I run my example using mvn jetty:run everything works just fine as expected. But when I deploy my application to my glassfish 3 container I get the following error message:
> com.sun.xml.ws.api.security.trust.WSTrustException: WST0017:Could not obtain STS metadata. MEX call to STS http://my.server.org:8081/SecurityTokenService/UT/mex failed.
> Looking into the STS Server Log it contains the following errors:
> [#|2011-12-05T17:28:46.222+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=20;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint.
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:144)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:123)
> [#|2011-12-05T17:28:46.235+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=19;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown.
> at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3954) Could not obtain STS metadata. MEX
call failed
Posted by "Glen Mazza (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163045#comment-13163045 ]
Glen Mazza commented on CXF-3954:
---------------------------------
As Dan said, I think the primary issue is to make sure your client is using the CXF libraries and not the built-in Metro/JAX-WS ones (if your goal is indeed to use a CXF client.)
I believe you're using the CXF STS, correct? If so make sure you have the WS-MetadataExchange dependency declared in your CXF STS:
https://cwiki.apache.org/confluence/display/CXF20DOC/WS-MetadataExchange -- you shouldn't need the SOAP 1.2 endpoints with that. AFAIK it's just the Metro clients making the MEX calls to the STS before they make the token requests, I don't believe (?) CXF clients make MEX calls by default.
I have some test cases of a CXF STS (on Tomcat) and a Metro WSC accessible here: http://java.net/jira/browse/WSIT-1590 -- while the MEX calls work for the Metro WSC, subsequent problems downstream are occurring, hence this particular bug report. But the Metro WSC -> CXF STS MEX calls work at least.
> Could not obtain STS metadata. MEX call failed
> ----------------------------------------------
>
> Key: CXF-3954
> URL: https://issues.apache.org/jira/browse/CXF-3954
> Project: CXF
> Issue Type: Bug
> Components: Services
> Affects Versions: 2.5
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: /opt/maven
> Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
> Java home: /usr/java/jdk1.6.0_25/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-71.el6.x86_64", arch: "amd64", family: "unix"
> Reporter: Jan Bernhardt
> Labels: mex, securitytokenservice, sts, sts-client
> Fix For: NeedMoreInfo
>
>
> I tried to deploy a cxf consumer as part of a servlet webapplication. When I run my example using mvn jetty:run everything works just fine as expected. But when I deploy my application to my glassfish 3 container I get the following error message:
> com.sun.xml.ws.api.security.trust.WSTrustException: WST0017:Could not obtain STS metadata. MEX call to STS http://my.server.org:8081/SecurityTokenService/UT/mex failed.
> Looking into the STS Server Log it contains the following errors:
> [#|2011-12-05T17:28:46.222+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=20;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint.
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:144)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:123)
> [#|2011-12-05T17:28:46.235+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=19;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown.
> at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3954) Could not obtain STS metadata. MEX
call failed
Posted by "Jan Bernhardt (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163426#comment-13163426 ]
Jan Bernhardt commented on CXF-3954:
------------------------------------
Hi, thanks for the fast and helpful responses.
It sounds plausible that my client uses the metro JAX-WS libraries, instead of the desired cxf ones. But how can I ensure, that my client uses the libraries provided by cxf? My service proxy classes have been generated by cxf-codegen-plugin and in my client pom file the following dependency was already contained:
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-jaxws</artifactId>
<version>${cxf.version}</version>
</dependency>
I also added the WS-MetadataExchange dependency to my STS, but it is still not working. At least I get a different error message:
com.sun.xml.ws.api.security.trust.WSTrustException: WST0042:No matching service with endpoint http://my.server.org:8081/SecurityTokenService/ found in the Metadata.
Do I need to provide some additional configuration to enable MEX Support?
> Could not obtain STS metadata. MEX call failed
> ----------------------------------------------
>
> Key: CXF-3954
> URL: https://issues.apache.org/jira/browse/CXF-3954
> Project: CXF
> Issue Type: Bug
> Components: Services
> Affects Versions: 2.5
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: /opt/maven
> Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
> Java home: /usr/java/jdk1.6.0_25/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-71.el6.x86_64", arch: "amd64", family: "unix"
> Reporter: Jan Bernhardt
> Labels: mex, securitytokenservice, sts, sts-client
> Fix For: NeedMoreInfo
>
>
> I tried to deploy a cxf consumer as part of a servlet webapplication. When I run my example using mvn jetty:run everything works just fine as expected. But when I deploy my application to my glassfish 3 container I get the following error message:
> com.sun.xml.ws.api.security.trust.WSTrustException: WST0017:Could not obtain STS metadata. MEX call to STS http://my.server.org:8081/SecurityTokenService/UT/mex failed.
> Looking into the STS Server Log it contains the following errors:
> [#|2011-12-05T17:28:46.222+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=20;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint.
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:144)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:123)
> [#|2011-12-05T17:28:46.235+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=19;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown.
> at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3954) Could not obtain STS metadata. MEX
call failed
Posted by "Jan Bernhardt (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163436#comment-13163436 ]
Jan Bernhardt commented on CXF-3954:
------------------------------------
I discovered my first question (disable metro jax-ws libraries) by myself:
http://cxf.apache.org/docs/application-server-specific-configuration-guide.html#ApplicationServerSpecificConfigurationGuide-Glassfish
Now my example is working as expected within glassfish. It would still be nice, to get the MEX Interface working, but at least for me (and the moment) it is not mandatory to me.
> Could not obtain STS metadata. MEX call failed
> ----------------------------------------------
>
> Key: CXF-3954
> URL: https://issues.apache.org/jira/browse/CXF-3954
> Project: CXF
> Issue Type: Bug
> Components: Services
> Affects Versions: 2.5
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: /opt/maven
> Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
> Java home: /usr/java/jdk1.6.0_25/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-71.el6.x86_64", arch: "amd64", family: "unix"
> Reporter: Jan Bernhardt
> Labels: mex, securitytokenservice, sts, sts-client
> Fix For: NeedMoreInfo
>
>
> I tried to deploy a cxf consumer as part of a servlet webapplication. When I run my example using mvn jetty:run everything works just fine as expected. But when I deploy my application to my glassfish 3 container I get the following error message:
> com.sun.xml.ws.api.security.trust.WSTrustException: WST0017:Could not obtain STS metadata. MEX call to STS http://my.server.org:8081/SecurityTokenService/UT/mex failed.
> Looking into the STS Server Log it contains the following errors:
> [#|2011-12-05T17:28:46.222+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=20;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint.
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:144)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:123)
> [#|2011-12-05T17:28:46.235+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=19;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown.
> at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3954) Could not obtain STS metadata. MEX call
failed
Posted by "Daniel Kulp (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-3954:
-----------------------------
Fix Version/s: NeedMoreInfo
> Could not obtain STS metadata. MEX call failed
> ----------------------------------------------
>
> Key: CXF-3954
> URL: https://issues.apache.org/jira/browse/CXF-3954
> Project: CXF
> Issue Type: Bug
> Components: Services
> Affects Versions: 2.5
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: /opt/maven
> Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
> Java home: /usr/java/jdk1.6.0_25/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-71.el6.x86_64", arch: "amd64", family: "unix"
> Reporter: Jan Bernhardt
> Labels: mex, securitytokenservice, sts, sts-client
> Fix For: NeedMoreInfo
>
>
> I tried to deploy a cxf consumer as part of a servlet webapplication. When I run my example using mvn jetty:run everything works just fine as expected. But when I deploy my application to my glassfish 3 container I get the following error message:
> com.sun.xml.ws.api.security.trust.WSTrustException: WST0017:Could not obtain STS metadata. MEX call to STS http://my.server.org:8081/SecurityTokenService/UT/mex failed.
> Looking into the STS Server Log it contains the following errors:
> [#|2011-12-05T17:28:46.222+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=20;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint.
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:144)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:123)
> [#|2011-12-05T17:28:46.235+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=19;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown.
> at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3954) Could not obtain STS metadata. MEX
call failed
Posted by "Daniel Kulp (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163026#comment-13163026 ]
Daniel Kulp commented on CXF-3954:
----------------------------------
This SOUNDS like it's not ending up using CXF on the client side but is using the Metro clients built into Glassfish. The Metro clients will send a series of MEX calls to the STS until one succeeds. It starts of with a couple of SOAP 1.2 calls, then tries some 1.1 calls. That can end up with a bunch of stack traces on the server side. One way to minimize this would be to enable SOAP 1.2 on the STS server. The first sets of calls should then work.
The error of:
com.sun.xml.ws.api.security.trust.WSTrustException: WST0017:Could not obtain STS metadata. MEX call to STS http://my.server.org:8081/SecurityTokenService/UT/mex failed.
more or less confirms that. com.sun.xml.ws.. class would be the metro based client.
> Could not obtain STS metadata. MEX call failed
> ----------------------------------------------
>
> Key: CXF-3954
> URL: https://issues.apache.org/jira/browse/CXF-3954
> Project: CXF
> Issue Type: Bug
> Components: Services
> Affects Versions: 2.5
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: /opt/maven
> Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
> Java home: /usr/java/jdk1.6.0_25/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-71.el6.x86_64", arch: "amd64", family: "unix"
> Reporter: Jan Bernhardt
> Labels: mex, securitytokenservice, sts, sts-client
>
> I tried to deploy a cxf consumer as part of a servlet webapplication. When I run my example using mvn jetty:run everything works just fine as expected. But when I deploy my application to my glassfish 3 container I get the following error message:
> com.sun.xml.ws.api.security.trust.WSTrustException: WST0017:Could not obtain STS metadata. MEX call to STS http://my.server.org:8081/SecurityTokenService/UT/mex failed.
> Looking into the STS Server Log it contains the following errors:
> [#|2011-12-05T17:28:46.222+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=20;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint.
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:144)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:123)
> [#|2011-12-05T17:28:46.235+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=19;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown.
> at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CXF-3954) Could not obtain STS metadata. MEX call
failed
Posted by "Jan Bernhardt (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Bernhardt closed CXF-3954.
------------------------------
Resolution: Not A Problem
Fix Version/s: (was: NeedMoreInfo)
Just an insufficient setup, not an cxf bug.
> Could not obtain STS metadata. MEX call failed
> ----------------------------------------------
>
> Key: CXF-3954
> URL: https://issues.apache.org/jira/browse/CXF-3954
> Project: CXF
> Issue Type: Bug
> Components: Services
> Affects Versions: 2.5
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: /opt/maven
> Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
> Java home: /usr/java/jdk1.6.0_25/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-71.el6.x86_64", arch: "amd64", family: "unix"
> Reporter: Jan Bernhardt
> Labels: mex, securitytokenservice, sts, sts-client
>
> I tried to deploy a cxf consumer as part of a servlet webapplication. When I run my example using mvn jetty:run everything works just fine as expected. But when I deploy my application to my glassfish 3 container I get the following error message:
> com.sun.xml.ws.api.security.trust.WSTrustException: WST0017:Could not obtain STS metadata. MEX call to STS http://my.server.org:8081/SecurityTokenService/UT/mex failed.
> Looking into the STS Server Log it contains the following errors:
> [#|2011-12-05T17:28:46.222+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=20;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint.
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:144)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:123)
> [#|2011-12-05T17:28:46.235+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=19;_ThreadName=Thread-2;|Interceptor for {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown.
> at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira