Hi,
We’re using the ClientApi for a Windows service subscribing to events from a durable topic. We expected the ClientApi library code to handle the connection between client and broker. But unfortunately we observe an unexpected behavior when network connection between client and broker is lost. Right after the connection is reestablished a number of exceptions are written to the console. The exceptions seem to indicate that the connection was manually closed before the AutorecoveringConnection could recover.
However, the connection is reestablished and the client continues to receive events on the topic after the reconnect. But if you try to close the client application it hangs during shutdown indicating that the library code is still holding references to some resources.
Steps to reproduce (see attached source code):
Questions:
Is it intentional that the client API outputs exceptions directly to the console?
Is it intentional that exceptions are thrown during connection recovery?
Is there any other way to use the ClientAPI to prevent getting exceptions from the library?
Product: NeuronEsb.ClientApi v 3.5.4 NuGet package
Platform: Windows 7 Professional 64 bit with Visual Studio Professional 2015 Update 3
Exceptions dumped in console (plus Console.WriteLine for the OnOffline and OnOnline events) and client attached
Thanks
Fabrizio
What's the version/build of the client api you are using? just right click the neuron.esb.dll
Hi Marty,
Neuron.esb.dll is version 3.0.0.0. Client API is taken from NuGet 3.5.4
ok...that's a real problem...
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin. Powered by