First off, make sure you are trying with the latest versions of CXF. You
don't specify what version you are using.
Some older web servers have issues with the default chunked requests that CXF
uses. If you can, I'd try configuring the conduit to turn off chunking,
maybe set the keep-alive to close. Possible that one of them may help.
Dan
On Monday, February 27, 2012 5:32:10 PM Barry Kern wrote:
> Hi,
>
> I have a jax-ws client configured via spring to hit an https web service.
> The first time I call my client to talk to the server the whole
> communication is successful. The second time I call my service to talk to
> the remote web service, I see the outbound soap message in my log but then
> I get javax.xml.ws.WebServiceException: Could not send Message and Caused
> by: java.net.SocketTimeoutException: SocketTimeoutException. If I manually
> copy and paste the outbound soap message to soap-ui - I get a response
> from the service quickly and I know the soap message is valid/the server is
> responding. If I restart my app the first call to the remote web service
> works again but subsequent calls fail. I am thinking perhaps this is a
> configuration issue on my part? my client is very basic and looks like
> this:
>
> <jaxws:client id="xxClient"
> serviceClass="com.fake.{path to web service}"
> address="https address here">
>
> <jaxws:outInterceptors>
> <ref bean="wss4jOut"/>
> </jaxws:outInterceptors>
>
>
> </jaxws:client>
>
> Thanks,
> Barry
--
Daniel Kulp
[email protected] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
