[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: PASOE error 18318 and 18320 in log file - connection timeout

Status
Not open for further replies.
G

Gareth Vincent

Guest
Monitoring via OEE console and yes these are ABL sessions. >> I'd be curious to know how you determine when things are locked. When monitoring the Sessions these particular users still show a connection to the "Agent ID" and when viewing the activity on the Agents screen one can observe that only some of the sessions id's are still processing user requests and this starts to narrow down when more users are stuck in reading/writing state. When all sessions are exhausted the user will end up with the error "Unable to connect to the Appserver....." In this particular example when looking at the agent.log and tracing the users Session ID the user was simply logging into the application with no errors in the log file. Our clients connect via Progress Webclient and by design our application makes 3 http connections to the Appserver per user. There are some asynchronous calls to the appserver to load dashboard widgets on login and to juggle between two frameworks. Simply trimming idle sessions is not always an option as some of these http connections can remain idle for some time while the other 1 or 2 http sessions are being used more often throughout the application. Trimming just one of the 3 http sessions can crash the application. We have over 400 client databases in our DC so you can imagine that can become difficult to manage even with the provided Rest API. There is always going to be connectivity issues to some degree and I would expect PASOE to handle these connections without any human intervention. I will play around with the "session-timeout" parameter as you mentioned to see if that helps. I keep finding myself comparing the Classic appserver to PASOE. If we are going to migrate I would expect nothing less that it to be as stable and to provide the same if not better performance than the Classic appsever. Up to this point neither has been the case. To be fair the performance issue that we had where the performance was 10 times slower is being addressed and a patch will be released. Moving to OE 12 is definitely not an option at this point and will not be for quite some time. I will keep you posted.

Continue reading...
 
Status
Not open for further replies.
Top