WCF EVent Monitor

[Guest Jonah]

A simalar incident occurred again today. I am not sure if this is directly related but for some reason it just dropped the calls (about 10) then recovered. However, the calls that were dropped were lost. This happened at approximately 3:24 PM. I have attached the logs. Please let me know if you need more information.

0721_1521_vgEngine.zip

[SupportTeam]

It looks like you are using an external application to communicate with VoiceGuide and are setting it up to receive events from VoiceGuide as well.

 

Trace shows that for 30 seconds between 15:23:57 and 15:24:27 VoiceGuide was trying to send events to the external application but the WCF system reported that events could not be forwarded.

 

VoiceGuide did not drop any calls or was affected by this in any way. Entries in log were made noting that that events were not delivered, and VoiceGuide went on with running the script.

 

It is possible to setup the WCF messaging system to write logs of its own. You would probably need those logs to see why WCF reported that: "ServiceChannel cannot be used for communication because it has been Aborted." and then 30 seconds later it was up again. If the external application has any logs then you should probably look at these as well.

 

Overall this looks like a different issue then outbound calls issue that this thread was initially about.

[Guest Jonah]

"It is possible to setup the WCF messaging system to write logs of its own"

 

How do I do this?

 

Thanks

[SupportTeam]

Searching for "WCF logging" in Google brings up a few links.

 

Probably start off by reading the Microsoft's documentation articles and then look at a few examples in blogs etc. You can configure the logging as part of the configuration file for WCF or programatically from within the code.

[Guest Jonah]

I am just using a modified version of the WCF_Demo app. Do you have the ability to create logs from that? Do you ever experience this issue if you leave the Deom app running for an extended period of time?

[SupportTeam]

You would need to add the WCF logging settings to the supplied demo application. The supplied demo application does not come with WCF logging enabling configuration. It is a demo app demonstrating WCF connectivity and the issuing of commands to VoiceGuide over WCF and receiving events over WCF.

 

No issues with WCF communications link were observed on our test systems.

[Guest Jonah]

If you launch the WCF_Demo app and then run a series of calls for 6 to 8 hours, does the Demo app ever lose connectivity?

[SupportTeam]

We have not observed it lose connectivity, and the load testing runs go for significantly longer times then 6-8 hours.

[Guest Jonah]

The WCF Connectivity that I am using is in the WCF_Demo app. I have not made any changes to that part of the application. Is there any other way to monitor the VoiceGuide events other than WCF?

[SupportTeam]

Right now WCF is the only way to monitor events.

 

The reason why WCF lost connection on your system for 30 seconds can be system specific or related to any error in the code that handled prior WCF events. You would need to look at WCF logs and any logs that your app generates to see if anything abnormal happened immediately prior to the 30 second loss of connection.

 

As this WCF discussion is unrelated to the original thread topic the WCF posts will be split into own separate thread.

(original thread: http://voiceguide.com/forums/index.php?showtopic=6737)