« Return to Thread: CXF WS Proxy Hangs

Re: CXF WS Proxy Hangs

by redijedi :: Rate this Message:

Here's some of the Mule stdout if it helps:

********************************************************************************

ERROR 2008-10-03 12:08:05,793 [connector.http.0.receiver.4]
org.mule.service.DefaultServiceExceptionStrategy:
********************************************************************************
Message : Failed to route event via endpoint:
DefaultOutboundEndpoint{endpointUri=http://localhost:8080/service/soap,
connector=HttpConnector{this=26f9e5, started=true, initialised=true,
name='connector.http.0', disposed=false,
numberOfConcurrentTransactedReceivers=4,
createMultipleTransactedReceivers=true, connected=true,
supportedProtocols=[http], serviceOverrides=null},
transformer=[ObjectToHttpClientMethodRequest{this=edbe39, name='null',
ignoreBadInput=false, returnClass=interface
org.apache.commons.httpclient.HttpMethod, sourceTypes=[interface
org.mule.api.MuleMessage, class [B, class java.lang.String, class
java.io.InputStream, interface org.mule.api.transport.OutputHandler,
class org.mule.transport.NullPayload]}],
name='endpoint.http.localhost.8080.service.soap', properties={},
transactionConfig=Transaction{factory=null, action=NEVER, timeout=0},
filter=null, deleteUnacceptedMessages=false, securityFilter=null,
synchronous=true, initialState=started, remoteSync=true,
remoteSyncTimeout=3000, endpointEncoding=UTF-8}. Message payload is of
type: PostMethod
Type : org.mule.api.transport.DispatchException
Code : MULE_ERROR-42999
JavaDoc :
http://mule.mulesource.org/docs/apidocs/org/mule/api/transport/DispatchException.html
Payload : org.apache.commons.httpclient.methods.PostMethod@1dfd90f
********************************************************************************
Exception stack is:
1. Content must be set before entity is written
(java.lang.IllegalStateException)
org.apache.commons.httpclient.methods.InputStreamRequestEntity:177
(http://java.sun.com/j2se/1.5.0/docs/api/java/lang/IllegalStateException.html)
2. Failed to route event via endpoint:
DefaultOutboundEndpoint{endpointUri=http://localhost:8080/service/soap,
connector=HttpConnector{this=26f9e5, started=true, initialised=true,
name='connector.http.0', disposed=false,
numberOfConcurrentTransactedReceivers=4,
createMultipleTransactedReceivers=true, connected=true,
supportedProtocols=[http], serviceOverrides=null},
transformer=[ObjectToHttpClientMethodRequest{this=edbe39, name='null',
ignoreBadInput=false, returnClass=interface
org.apache.commons.httpclient.HttpMethod, sourceTypes=[interface
org.mule.api.MuleMessage, class [B, class java.lang.String, class
java.io.InputStream, interface org.mule.api.transport.OutputHandler,
class org.mule.transport.NullPayload]}],
name='endpoint.http.localhost.8080.service.soap', properties={},
transactionConfig=Transaction{factory=null, action=NEVER, timeout=0},
filter=null, deleteUnacceptedMessages=false, securityFilter=null,
synchronous=true, initialState=started, remoteSync=true,
remoteSyncTimeout=3000, endpointEncoding=UTF-8}. Message payload is of
type: PostMethod (org.mule.api.transport.DispatchException)
org.mule.transport.http.HttpClientMessageDispatcher:120
(http://mule.mulesource.org/docs/apidocs/org/mule/api/transport/DispatchException.html)
********************************************************************************

On Fri, Oct 3, 2008 at 12:25 PM, Todd Orr <torr0101@...> wrote:

> I'm attempting to simply proxy an existing WS for version management,
> etc. At this point all I'm trying to do is simply pass requests from
> the new endpoint to the existing one. I've read this doc
> (http://www.mulesource.org/display/MULE2USER/Proxying+Web+Services) on
> how to do it, but it's not working out so well. My config is as
> follows:
>
>
> <service name="service">
>
> <inbound>
>
> <cxf:inbound-endpoint
> address="http://localhost:63081/service"
> proxy="true" />
>
> </inbound>
>
>
> <outbound>
>
> <outbound-pass-through-router>
>
> <cxf:outbound-endpoint
> address="http://localhost:8080/service/soap"
> proxy="true" />
>
> </outbound-pass-through-router>
>
> </outbound>
>
> </service>
>
>
> This appears to be inline with the doc. The first thing I noted is
> that it's not presenting the proxied WSDL. The original WSDL at
> http://localhost:8080/service/soap?wsdl is correct, but the WSDL at
> http://localhost:63081/service?wsdl refers to the ProxyService and is
> completely different. However, the client can still connect, so I'm
> willing to live with this oddity if I can get this functional even
> though it'd be nice to not have to.
>
> The bigger issue is that when a client that was previously working
> when configured to hit the original service address attempts to use
> the new address it hangs, then times out. Looking at the stdout of
> mule I see that it receives and passes on a request, but immediately
> closing the HTTP connections. It hangs too until it times out. Upon
> timing out, or maybe just before (it happens very quickly) something
> is sent to the original address, but it appears as if no parameters
> are sent. I get output on the stdout of the JBoss instance hosting the
> original service that shows that the correct operation was called, but
> with no arguments.
>
> I've fiddled with all combinations of synchronous and asyncRemote with
> no change.
>
> This is day 2 of trying to solve this. I've already googled the crap
> out of the issue and am officially tired. Any help is greatly
> appreciated.
>
> Thanks,
> T
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

« Return to Thread: CXF WS Proxy Hangs