Hey guys,
First off, thanks so much for this project, it's helped me out an incredible deal.
I wanted to reach out because I'm running into an issue and am not sure if I'm just doing something wrong or have found an issue.
I'm using SqlServer 2016, and running the service in a pretty simple manner. I've got it running in a console window, monitoring a single table. Changing table records triggers the event just like it should, but what I found was the service would always crash when I stopped the app, crashing specifically in the Uninstall method.
What was happening was the cleanup method was timing out, which I eventually ran down to the fact that, after a few hours or days of the app running, was that the conversation_endpoints table was just filled with thousands, sometimes tens or even hundreds of thousands, of DISCONNECTED_INBOUND records.
Looking around, I was that things like this could happen when conversations weren't properly "ended" (A fire and forget kind of scenario, right?). Is there something else I need to do to prevent this from occurring?
Hey guys,
First off, thanks so much for this project, it's helped me out an incredible deal.
I wanted to reach out because I'm running into an issue and am not sure if I'm just doing something wrong or have found an issue.
I'm using SqlServer 2016, and running the service in a pretty simple manner. I've got it running in a console window, monitoring a single table. Changing table records triggers the event just like it should, but what I found was the service would always crash when I stopped the app, crashing specifically in the Uninstall method.
What was happening was the cleanup method was timing out, which I eventually ran down to the fact that, after a few hours or days of the app running, was that the conversation_endpoints table was just filled with thousands, sometimes tens or even hundreds of thousands, of DISCONNECTED_INBOUND records.
Looking around, I was that things like this could happen when conversations weren't properly "ended" (A fire and forget kind of scenario, right?). Is there something else I need to do to prevent this from occurring?