I
Irfan
Guest
David, The way OpenClients work is that once they disconnect they have to release the connections, if they do not then we should be seeing hung clients/connections. To be safe, dotnet clients should configure their timeout properties(IdleSessionTimeout,ConnectionTimeout,ConnectionLifetime etc). From PASOE, we can enable IdleResourcetimeout and enable appropriate property(like idleConnectionTimeout) if we want to cancel or terminate the connections that might be hanging around. This should mitigate the problem of terminating stale sessions/connections in PASOE instance and should not require any restart of the PASOE server. I am not sure if this is relevant to your case, but thought of letting you know in-case you were looking for options. To determine you have idle connections, I would prefer accessing the API - localhost:8810/.../sessions If this gives any results then it means that you have sessions/connections hanging. I see that you tried to access sessions but you do not see anything in the response. With PASOE Development server, the max connections or requests you can make would be only 5. You can actually make more than 5 requests but only 5 will be handled in the given time. So the remaining requests will fail with the error you have mentioned. To make sure that the sessions are IDLE and waiting for the next requests, I would look for the number of sessions you currently have and what is the status of it. I would first look at the MS-Agent /sessions API and see if I have used up all the 5 sessions. If any of the sessions status is ACTIVE, then I would see the session stacks to know what that session is doing. MS-Agent sessions - localhost:7810/.../sessions MS-Agent Session stacks - localhost:7810/.../stacks Another way to see is all the sessions were used would be to look at the agent log. The MS-Agent sessions in the agent log can be identified with 'AS- '. In my case, where I was running a development license, If I run for 50 concurrent clients, I got same errors as you have experienced and I can see in my agent log that all my 5 MS-Agent ABL Sessions were utilized. So please look at the agent log and see how many sessions were used up. cat testinst.agent.log | grep 'AS-' | cut -d ' ' -f 5 | uniq | sort -u AS-10 AS-4 AS-7 AS-8 AS-9 AS-Admin AS-Aux-0 AS-Aux-5 AS-Aux-6 AS-Listener AS-ResourceMgr This should tell us why you were seeing the error. It might have happened that the client was disconnected for some reason, but the MS-Agent sessions are still running the application logic. If you do not see all the 5 sessions used up then I sense a bug in the Product for PASOE dev license.
Continue reading...
Continue reading...