Hold not working in 3.8.1P

[Brian Goad]

Has anyone experienced the HOLD/RELEASE feature in Network Monitor not holding messages as intended. According to the documentation the hold feature should hold outbound messages in the outbound queue. The Release feature releases any messages currently being held. What I have experienced is this:

I start a thread reading a large file and attempted to place it on “HOLD” messages continued across the interface. The icon on the thread did change to read “hold”. I stopped the recieving thread and the messages began to collect in the Route, the queue depth never stopped climbing.

Just wondering?

Brian

Topic

[Jim Kosloskey]

Brian,

Cloverleaf probably sucked in a lot of messages from the file (unless you throttled it) once you started the thread before your Hold command could be acted upon. Those messages will still continue through the engine. Those might be the messages you saw.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Michael Hertel]

Brian Goad wrote:

I start a thread reading a large file and attempted to place it on “HOLD” Brian

Hold/release only works on outbound threads.

Yes, the inbound thread will show hold status if clicked, but may only hold ACKS going back if it is socketed connection.

The other thing about reading large files in is that Cloverleaf seems to like to do things one step at a time. It will process all messages through the various states.

Example: you suck in 3600 messages. All 3600 go into state 1 then all 3600 go into state two and so on. It takes a fairly long time to do this and so the process may seem unresponsive but is really not. It’s just trying swallow a lot at one time.

[Author]

Replies