Friday, January 19, 2007

WSE2 Tracing SOAP messages

Microsoft Web Services Enhancements (WSE 2.0) allows you to trace incoming and out going SOAP message. Monitor the trace files and purge the files before they become too big. If the files get too big, WSE 2.0 throws all kind of communication errors.

My webservice is behind a firewall and is hosted in a windows service on a particular port (xxxx). The client (outside the firewall) communicates with the windows service over TCP.

One fine day, the communication between the client and service broke. I found the following stack trace in my log file. From the stack trace, my initial thought was the service might be down and verfied the service to be running. Next, I connected my local system to the service and verfied that the communicate is fine. Since the service is running properly, I verified with the sys admin that the port (xxxx) on the router is mapped correctly to the server hosting the webservice.

After banging my head and Googling for hours I could not come up with a definite reason on why the client could not communicate with the service. When I tried to open the trace files on the client, I realised them to be too big and right then I had that AHA moment. I went ahead and disabled WSE SOAP message tracing and you got it right, the app is back on its feet smiling.

Error Message:Write Failure: Socket is not connectedStack Trace:Server stack trace: at Microsoft.Web.Services2.Messaging.SoapTcpNetworkStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncCallback callback, Object state) at Microsoft.Web.Services2.Messaging.SoapTcpNetworkStream.Write(Byte[] buffer, Int32 offset, Int32 count) at Microsoft.Web.Services2.Dime.DimeRecord.WriteHeader(Boolean endOfRecord, Int64 contentLength) at Microsoft.Web.Services2.Dime.DimeRecord.WriteChunkedPayload(Boolean endOfRecord, Boolean endOfMessage, Byte[] bytes, Int32 offset, Int32 count) at Microsoft.Web.Services2.Dime.DimeRecord.WriteChunkedPayload(Boolean endOfRecord, Boolean endOfMessage) at Microsoft.Web.Services2.Dime.DimeRecord.Close(Boolean endOfMessage) at Microsoft.Web.Services2.Dime.DimeWriter.Close() at Microsoft.Web.Services2.Messaging.SoapDimeFormatter.Microsoft.Web.Services2.Messaging.ISoapFormatter.Serialize(SoapEnvelope envelope, Stream stream) at Microsoft.Web.Services2.Messaging.SoapTcpConnection.SerializeMessage(SoapEnvelope envelope) at Microsoft.Web.Services2.Messaging.SoapTcpOutputChannel.Send(SoapEnvelope message) at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase) at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData) at Microsoft.Web.Services2.Messaging.SendDelegate.EndInvoke(IAsyncResult result) at Microsoft.Web.Services2.Messaging.SoapOutputChannel.EndSend(IAsyncResult result) at Microsoft.Web.Services2.Messaging.SoapSender.EndSend(IAsyncResult result) at Microsoft.Web.Services2.Messaging.SoapClientAsyncResult.OnSendComplete(IAsyncResult result)

Digg It! Add to Stumble This