M
MBeynon
Guest
Hello, I wonder if someone could give me a little advice please? We have a client who is concerned about the load being placed on their production Appserver, specifically the number of Agents SENDING and the client queue depth. Currently they have a maximum of ten licensed Agents configured and according to the stats, all ten are busy on most days. At two points during the last month, our clients became concerned with the client queue depth which began creeping up and at one point "maxed-out" at 145 before dropping down to the 40's and 50's. They are concerned about this and the subsequent drop in response times to the incoming requests. I've done a search on the knowledgebase and found this: http://knowledgebase.progress.com/articles/Article/P83089 which talks about possible reasons for agents being in the sending state for longer than expected: 1. In both SENDING or LOCKED States, the Agent could be stuck because it lost the connection to the AppServer client it's currently associated with. This is typically due to Network issues interrupting the TCP/IP connection or because the client crashed/was killed, terminated their session abnormally. 2.If the Appserver Agent stays in the state of SENDING for a long time a programming scoping issue can cause a lot more data to be returned than expected, via the Broker, from the AppServer to the client (for example: Temp-tables or datasets that contain many more records than expected). With regards to point one, how does this happen and is there anything that can be done to mitigate this? I'm going to suggest our client "Set the AppServer logging mode to VERBOSE (srvrLoggingLevel=3 in uBroker.properties) in order to find what procedures are running by the Agents identified by their PID." and also review our code for memory leaks, but if anyone has any thoughts, comments or suggestions I'd be most grateful. Thankyou, Mark. P.S. The appserver is STATELESS BTW.
Continue reading...
Continue reading...