- This topic has 1 reply, 2 voices, and was last updated 12 years ago by .
-
Topic
-
I might be missing something on this feature – or don’t have it setup correctly, but I have some discomfort deploying this feature b/c: 1) it doesn’t show a status (up/down) in netmonitor (our ops are tuned to the colors).
2) I can’t see any queue depth
3) I can’t stop and start the destination thread
4) If I stop the receiving thread process, then I can’t get the process back up b/c the public port is allocated to the destination thread. I have to drop the destination thread process to start the receiving process.
I understand the need to reduce thread count, and I certainly appreciate the feature progress, but if this isn’t a user setup error, I inclined to continue the old practices.
My $.02 – please tell me if I’m just not doing something right….
- The forum ‘Cloverleaf’ is closed to new topics and replies.