There are several tools that will allow you to monitor the EMS and specific destinations. The exceptions thrown by the client depend on the problem, they all inherit from and they are all listed in your API documentation(!). In the second case the number of attempts depends on how the connection factory is configured (ask your EMS administrator). I suggest you log this internally just above the client dll level (see next question).ĭepending on the specific problem the EMS client dlls will either throw an exception or in the case of a lost connection, attempt to reconnect. I suggest log4Net or similar library for that. What is it exactly that you want to monitor, is it the actual messages on the bus/EMS or the workings of your client (not including the client libraries)? The first I'll answer below, the second you can handle with regular logging.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |