- This topic has 5 replies, 2 voices, and was last updated 4 years ago by
.
Viewing 2 reply threads
Viewing 2 reply threads
- You must be logged in to reply to this topic.
kimbomadsen.
Babis MichaelHello,
Setting anything above 1 on ClientConnectionPool.MaxConnections it will raise EIdAlreadyConnected.
Tried both with Autoactivate on and off.
Any ideas ?
Thanks
kimbomadsenHi,
No… I can’t say I have…. are you using standard request/response transports or WIB?
/Kim
Babis MichaelI’m using Indy TCP Messaging with kbmMWClientQueries.
I had to increase it because i was getting: PooledDataset : ObtainConnection : Timeout/error waiting for connection.
Before 5.06.20 July 11 2018 which included that “AutoActivate” on TkbmMWCustomConnectionPool it worked.
Thank you
kimbomadsenIt does not make sense to increase it when using messaging transports. In that case it should always be left at default or 1.
The reason is that messaging transports will handle multiple ongoing requests at the same time.
So I think something else must be going on.
/Kim
Babis MichaelFrom my side or kbmMW ?
kimbomadsenSomething else must be going on in the code that makes you try to increase MaxConnections.
Messaging transports only opens one connection due to it being async, and thus not blocking during a request/resppnse, allowing multiple threads to do multiple requests at the same time over the same single connection.
/Kim