cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (Commented) (JIRA)" <>
Subject [jira] [Commented] (CXF-3954) Could not obtain STS metadata. MEX call failed
Date Mon, 05 Dec 2011 20:36:40 GMT


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: WST0017:Could not obtain STS metadata.
MEX call to STS failed.

more or less confirms that. class would be the metro based client.

> Could not obtain STS metadata. MEX call failed
> ----------------------------------------------
>                 Key: CXF-3954
>                 URL:
>             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:
> WST0017:Could not obtain STS metadata.
MEX call to STS 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 {}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(
>         at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(
>         at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
>         at org.apache.cxf.transport.ChainInitiationObserver.onMessage(
> [#|2011-12-05T17:28:46.235+0100|WARNING|glassfish3.1.1|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=19;_ThreadName=Thread-2;|Interceptor
for {}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(
>         at org.apache.cxf.interceptor.ServiceInvokerInterceptor$
>         at java.util.concurrent.Executors$
>         at java.util.concurrent.FutureTask$Sync.innerRun(
>         at
>         at org.apache.cxf.workqueue.SynchronousExecutor.execute(
>         at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message