Hi Dan,
I saw that almost all the time is lost between the WSS4JInInterceptor and the
caught of the exception by the caller on Client side.
Seems that the exception arrives soon at the client but after the
WSS4JInInterceptor there is a loss of time.
Tha stack of calls should be the following:
when the response arrives in the WSS4JInInterceptor, it prints
LOG.warning("Request does not contain Security header, " + "but it's a
fault.");
then, we arrive in the ClientImpl class
private Object[] doInvoke(ClientCallback callback,
BindingOperationInfo oi,
Object[] params,
Map<String, Object> context,
Exchange exchange) throws
Exception {...}
and execute the:
return processResult(message, exchange, oi, resContext);
So we arrive in the
protected Object[] processResult(Message message,
Exchange exchange,
BindingOperationInfo oi,
Map<String, Object> resContext) throws
Exception {
and block here:
// Wait for a response if we need to
if (oi != null && !oi.getOperationInfo().isOneWay()) {
synchronized (exchange) {
waitResponse(exchange);
}
}
We exit from the "waitResponse" statement after more than 30 seconds with the
print:
"Timed out waiting for response to operation"
Any suggestion?
It could be caused by the malformed message reported by the WSS4JInInterceptor?
Thanks,
Andrea
Date: Fri, 31 May 2013 09:11:20 -0700
From: [email protected]
To: [email protected]
Subject: Re: WebServiceException is not propagated from Provider<Source> to the
client.
On May 31, 2013, at 11:20 AM, eanbiso <[hidden email]> wrote:
> Sorry, I was wrong:
> the exception arrives to the client but very late (with almost a minute of
> delay).
> Seems to have lost a lot of time in the chain of interceptors on the
> dispatcher.
> I try to investigate it and get more info.
Wow. That's strange. Sounds like a flush or close isn't being called on the
output stream, but that SHOULD be the same for a regular call as for an
exception case. Strange.
Dan
>
> Andrea
>
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/WebServiceException-is-not-propagated-from-Provider-Source-to-the-client-tp5728573p5728589.html
> Sent from the cxf-user mailing list archive at Nabble.com.
--
Daniel Kulp
[hidden email] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
If you reply to this email, your message will be added to the
discussion below:
http://cxf.547215.n5.nabble.com/WebServiceException-is-not-propagated-from-Provider-Source-to-the-client-tp5728573p5728595.html
To unsubscribe from WebServiceException is not propagated from
Provider<Source> to the client., click here.
NAML
--
View this message in context:
http://cxf.547215.n5.nabble.com/WebServiceException-is-not-propagated-from-Provider-Source-to-the-client-tp5728573p5728621.html
Sent from the cxf-user mailing list archive at Nabble.com.
