A few answers: You say you copy and paste the SOAP request to soapUI and run it there--is it also encrypted (with same keys, etc.) when run from soapUI, or is it clear text there?
The soap request is logged to the console before going to the wire so it is clear text. I paste that in soap-ui and then send it to the https webservice. Also, can you make multiple consecutive calls with soapUI ? Yes , I can't replicate via soap-ui (many successive calls work) I did watch with Wireshark and saw a difference in the packets exchanged but I couldn't determine any action steps to take I will try alternate client and some more investigation today and reply. Thanks, Barry On Mon, Feb 27, 2012 at 10:54 PM, Glen Mazza <[email protected]> wrote: > Perhaps something strange going on in your Spring configuration, [1] might > help--constructing a different Java client and seeing if you can make > consecutive calls with it. I would also check the working & failing calls > with Wireshark[1]--although the calls will be encrypted so you won't be > able to see much there might be something radically different/corrupted > with the second call. > > You say you copy and paste the SOAP request to soapUI and run it there--is > it also encrypted (with same keys, etc.) when run from soapUI, or is it > clear text there? Your SOAP client is using the SSL, so if soapUI is using > clear text it may not be proving much. Also, can you make multiple > consecutive calls with soapUI--remember the first call works with your Java > client, so successful running with soapUI could just be a case of the > "first call works" without showing much else. > > Glen > > [1] > http://www.jroller.com/gmazza/**entry/blog_article_index<http://www.jroller.com/gmazza/entry/blog_article_index>(link > #1, #11, #33) > > > On 02/27/2012 06:32 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 >> >> > > -- > Glen Mazza > Talend Community Coders - coders.talend.com > blog: www.jroller.com/gmazza > >
