Hi Tom - thanks for the description and sorry for using confusing terms as I’m getting used to these now :).
I checked with my admin and he confirmed that we are not using JMS. What we are using is “Direct” mode of messaging with Non-durable queues and the client applications are subscribing to topics.
The problem we are facing is - the client applications run fine during the day, but when it is shutdown at 11:00 pm, the client application does an Unsubscribe() for all the topics it has subscribed to and then kills the exe.
During this attempt of unsubscribe(), one of the client instance appears as slow subscriber in SolAdmin and the connection appears to be open, but in the client app logs - we see the unsubscribe() call is complete and the connection is closed and exe is also killed. This remains open the next day until when we disconnect manually from SolAdmin.
In above case , the message spool quota was breached due to the Egress discards.
My main concern here is that when the clientApp.exe is killed - why does the connections remain open on solace side?
How do I ensure that nothing remains on solace when my exe is closed? we are using SolClient.Messaging.dll to call the Unsubscribe() method in a .Net client application.
How can we configure solace such that - if there is any client process that is popping up as a slow subscriber - can solace disconnect the client automatically?
Thanks in advance
Rajesh