D
dbeavon
Guest
Are you using the APSV transport with HTTP sessions enabled? Is it every single client connection that is behaving this way or just certain ones? What does the user experience in the remote client process when this happens? I'd probably use agent tracing (log entry type 4GLTrace) to see if you can find out the last thing that the bad ones do before they get stuck in "ACTIVE". You might find a pattern. The fact that you can't get a stack trace is not in itself unusual. I think that feature is a bit unreliable, and I have seen that happen when things are operating normally. But I would agree that it is a problem for your ABL sessions to remain stuck at ACTIVE. FYI, If you are using HTTP sessions then I've found that the tomcat "manager" webapp has quite a lot of power to free things up again in a pinch. The HTTP session from tomcat essentially becomes the master-key for all related resources in PASOE (both in the java-session-manager and in the ABL-ms-agents). If you forcefully expire/disconnect HTTP sessions in the tomcat "manager" webapp and it doesn't free up the related resources in PASOE then that is almost certainly a Progress bug. I would definitely deploy that "manager" webapp and try to force-expire all of the HTTP sessions and see what happens.
Continue reading...
Continue reading...