- This topic has 6 replies, 2 voices, and was last updated 3 years, 5 months ago by
.
Viewing 2 reply threads
Viewing 2 reply threads
- You must be logged in to reply to this topic.
Babis Michael.
Babis MichaelHello,
Any ideas why the queries timeout after some time running the server ? (randomly)
It seems like the server doesn’t accept new connections!
Thank you
Babis MichaelThe client actually waits a response from the server in the function TkbmMWEvent.WaitFor … sleep(n); …. but never get its … although the server works without problens! Seems like something is filling up the connections pool but never releases them back from the server side ?
Thank you
kimbomadsenHi,
What type transport are you using?
/Kim/C4D
Babis MichaelIndy Messaging! (Using messages and services)
Babis MichaelIt seems messages stuck in InBound message queue and increasing over time!
kimbomadsenThose messages may somehow throw exceptions and be rolled back to the queue. If no stall detection is defined, then they will stick there.
However I have seen relatively rare situations where the Indy transport implementation may not provide a complete message to the messaging framework. It is changed with the native messaging transport, which handles all the packet fragment collection itself.
/Kim/C4D
Babis MichaelWell Reject and Delete StalledMessages is true by default, anyhow i’ve added Reject and Stall Queues to monitor. Let’s see!
Can’t wait to try the native messaging transport! 🙂
Thank you