ServiceControl - Body Missing In Xml View - Unable to read data from the transport connection

[JeffreyAllenMiller]

ServiceControl Team,

We have been experiencing issues with ServiceControl where the XML tab of the body is blank but the Hex tab is not. When this occurs we receive the following error in the Log tab.

2014-08-25 10:27:37.362 -04:00 [Information] HTTP GET http://SHSDSH-AUDT01T:33333/api/messages/055df7d5-ea59-4c5f-9241-a392009c818d/body
2014-08-25 10:27:37.388 -04:00 [Error] Error executing the request: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host., Status code is 0
System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
--- End of inner exception stack trace ---
at System.Net.GZipWrapperStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at RestSharp.Extensions.MiscExtensions.ReadAsBytes(Stream input)
at RestSharp.Http.ProcessResponseStream(Stream webResponseStream, HttpResponse response)
at RestSharp.Http.ExtractResponseData(HttpResponse response, HttpWebResponse webResponse)
at RestSharp.Http.GetResponse(HttpWebRequest request)

Note that I also tried this using version 1.1 and 1.7 and we get the same results. It is curious that the Hex tab is populated. Also the flow diagram and header tabs are populated correctly. Note we are using the default xml serializer in our end points. This is impacting our ability to trouble shoot issues, any assistance you can provide would be greatly appreciated. On a side note, it would be a nice if the Hex view had the ability to copy the hex values as well as the resulting text to the clip board. This would be handy and would be a work around when there are issues using the xml tab. Lastly, and perhaps most importantly, I believe the issue has to deal with they way we are sending our messages or what you are expecting the payload to be. Let me explain. We have a command class called EventCommand that we send to our dedicated publisher service. The event command takes has two properties and EventPayload and an EventPayloadTypeName. The EventPayload gets populated with a s serialized object that implements NServiceBus.IEvent and EventPayloadTypeName represents the type of the object that was assigned to EventPayload. Basically, we are bundling up events that we want to publish but are sending them to a publisher service where they are deserialize and ultimately published via Bus.Publish. I thought is that there is an issue with the serialization on our side or service insights. For what it is worth the messages show up perfectly in Cogin Queue Explore and obviously we are able to publish them which has been working for a year now. I attached an example .mq and the code we are using - any assistance would be greatly appreciated.

Looks like you do not support uploading code or .mq so I will dumped some screen shots.

    {

[JeffreyAllenMiller]

For what it is worth it looks like the hex view is also getting cut off. So maybe there is some character you are keying off that is throwing things out of whack.

[JeffreyAllenMiller]

I could look into Url or Base64 encoding the payload as well, but am reluctant to start going down that path until I hear ServiceControls' perspective. Note that sometimes these objects are viewable in ServiceControl all the more reason I am a little hesitant, plus they will not be very readable in servicecontrol if I encode them. On a side note, I don't know if this scenario is unique to us, but assuming we have to encode part the payload, it would be very convenient to have a feature in SC where you could select part of the text and right click a context window to pop up the results after applying some decoding.

[indualagarsamy]

@JeffreyAllenMiller - Can you post your message definitions for which SI is having an issue displaying the message body?

[jdrat2000]

@JeffreyAllenMiller I just replied to your support ticket regarding this issue Jeff. Thank you.

[johnsimons]

Hi @JeffreyAllenMiller,

Your message contains an XDocument in it, is this right?
Anyway, I'll try to reproduce it.

[johnsimons]

@JeffreyAllenMiller can you send us the SC logs?
And also the export of the message mq files?

[fredricadell]

We experience the same issue on some of our messages. The messages contains large strings with html tags in them because they are represented as emails.

2014-09-16 12:09:46.482 +02:00 [Error] Error executing the request: Unable to read data from the transport connection: En befintlig anslutning tvingades att stänga av fjärrvärddatorn., Status code is 0
System.IO.IOException: Unable to read data from the transport connection: En befintlig anslutning tvingades att stänga av fjärrvärddatorn. ---> System.Net.Sockets.SocketException: En befintlig anslutning tvingades att stänga av fjärrvärddatorn
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
--- End of inner exception stack trace ---
at System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at RestSharp.Extensions.MiscExtensions.ReadAsBytes(Stream input)
at RestSharp.Http.ProcessResponseStream(Stream webResponseStream, HttpResponse response)
at RestSharp.Http.ExtractResponseData(HttpResponse response, HttpWebResponse webResponse)
at RestSharp.Http.GetResponse(HttpWebRequest request)

[JeffreyAllenMiller]

Sorry for the delay, but our messages contain sensitive Health Insurance Portability and Accountability Act (HIPAA) information in them. In layman's terms it just means it contains sensitive patient information that we cannot share. I have brought this to my Managers attention and he is escalating the issue internally to see if perhaps we can get a non disclosure agreement or something in place that would enable use to send you the database.

John Simons: We are not using an XDocument, but rather just using a string for our properties.

Additionally, when we were spinning up our production environment and we had some initial hiccups. During that time, I manually deleted the collections in Service Control via the Silverlight Management module. It is my understanding that RavenDB would simply recreate the collections and everything should run smoothly when new messages come in. Could this have had any negative impact.

Fred Ricadell: We to have html or xml in our message payloads and suspect that might be related to the issue. However, I don't see the messages in RavenDB in most cases. Keep in mind that I barely no what I am doing with RavenDB and perhaps I querying it incorrect.

I will email Joe Ratzloff the SC logs, but keep in mind that some of the errors in there might be from me trying to figure out how to query RavenDB.

I will also try to get some code together to share as well. Assuming we can get over the HIPAA issue, do you have a site or something that I can upload the files to.

[indualagarsamy]

@JeffreyAllenMiller @fredricadell - Thanks for your inputs. I have been able to reproduce this issue on our end now. Investigating the problem. Will keep you posted.

[indualagarsamy]

moved to Particular/ServiceInsight#384