D
dbeavon
Guest
Thanks for the feedback. It is good to know that another customer tested OE 11.7 in an application that was open for longer than 30 mins.
Apparently what you described was the primary workaround. Have you taken this configuration to production yet? I had some concerns that it would only substitute one type of problem for another. When you turn off HTTP sessions for APSV in 11.7, my understanding is that it substitutes another type of session internally (it will start exclusively using the classic AIA APSV sessions.) See Progress KB - What are the types of OpenEdge sessions for discussion about PASOE sessions. From what I've seen these have no visibility in the OEE interface, making them very hard to manage, despite the fact that they are hosted inside the tomcat server process. I have concerns that they will be leaked over time, and cause memory problems especially in the context of our session-free connections, which is the primary type of connection that we use. The other problem I had with turning off HTTP sessions is that, being new to PASOE, I didn't want to use a customized and non-standard configuration. We also wanted to be able to use a Netscaler load balancer in front of PASOE for higher availability.
Continue reading...
Continue reading...