11-08-2013 03:56 AM
Hi,
we receive every ten minutes an new Warning in Application Eventlog on our SData-Server. Has anybody seen this?
We are on SLX8, Web Core 04, Web Model 03
2013-11-08 12:44:17,534 [19] WARN Sage.Platform.Messaging.Transport.Wcf.MessageBusCallback - Existing client faulted; initiating reconnect logic
{
"date": "2013-11-08T12:44:17",
"utc": "2013-11-08T11:44:17",
"stackTrace": " at Sage.Platform.Application.Diagnostics.Logger.LogEvent(ILog log, EventLogEntryType entryType, String message, UInt16 eventId, Exception exception, Boolean debug)\r\n at Sage.Platform.Messaging.Transport.Wcf.MessageBusCallback.HandleFaulted(Object sender, EventArgs e)\r\n at System.ServiceModel.Channels.CommunicationObject.OnFaulted()\r\n at System.ServiceModel.Channels.CommunicationObject.Fault()\r\n at System.ServiceModel.Channels.ServiceChannel.OnInnerChannelFaulted(Object sender, EventArgs e)\r\n at System.EventHandler.Invoke(Object sender, EventArgs e)\r\n at System.ServiceModel.Channels.CommunicationObject.OnFaulted()\r\n at System.ServiceModel.Channels.FramingDuplexSessionChannel.OnFaulted()\r\n at System.ServiceModel.Channels.CommunicationObject.Fault()\r\n at System.ServiceModel.Channels.FramingDuplexSessionChannel.EndReceive(IAsyncResult result)\r\n at System.ServiceModel.Channels.FramingDuplexSessionChannel.TryReceiveAsyncResult.OnReceive(IAsyncResult result)\r\n at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)\r\n at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)\r\n at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously, Exception exception)\r\n at System.ServiceModel.Channels.SynchronizedMessageSource.ReceiveAsyncResult.OnReceiveComplete(Object state)\r\n at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(Object state)\r\n at System.ServiceModel.Channels.StreamConnection.OnRead(IAsyncResult result)\r\n at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)\r\n at System.Net.LazyAsyncResult.Complete(IntPtr userToken)\r\n at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)\r\n at System.Net.AsyncProtocolRequest.CompleteWithError(Exception e)\r\n at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)\r\n at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)\r\n at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously, Exception exception)\r\n at System.ServiceModel.Channels.ConnectionStream.ReadAsyncResult.OnAsyncReadComplete(Object state)\r\n at System.ServiceModel.Channels.SocketConnection.FinishRead()\r\n at System.ServiceModel.Channels.SocketConnection.AsyncReadCallback(Boolean haveResult, Int32 error, Int32 bytesRead)\r\n at System.ServiceModel.Channels.OverlappedContext.CompleteCallback(UInt32 error, UInt32 numBytes, NativeOverlapped* nativeOverlapped)\r\n at System.Runtime.Fx.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)\r\n at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)\r\n",
"hashCode": "51FD8D93-C35C4D54-DA277528",
"pid": 840,
"identity": {
"name": "",
"isAuthenticated": false,
"authenticationType": ""
},
"version": "8.0.0.8556",
"logger": {
"level": "WARN",
"location": "Sage.Platform.Messaging.Transport.Wcf.MessageBusCallback.HandleFaulted(:0)",
"name": "Sage.Platform.Messaging.Transport.Wcf.MessageBusCallback",
"message": "Existing client faulted; initiating reconnect logic"
},
"request": null,
"server": {
"host": {
"siteName": "SalesLogix",
"applicationId": "/LM/W3SVC/2/ROOT/SData",
"applicationPhysicalPath": "C:\\inetpub\\wwwroot\\SData\\",
"applicationVirtualPath": "/SData"
}
}
}
Solved! Go to Solution.
11-10-2013 06:56 AM
This is a "no harm" warning, logging the fact that the Messaging Server, timedout it's connection and will reconnect. We are looking at how we can remove the Warning in future versions.
John Perona
Director, Infor CRM DevelopmentInfor CRM
11-10-2013 11:56 PM
Hi John,
thank you for your feedback. We will ignore this message.
11-18-2014 05:41 AM