D
dbeavon
Guest
Has anyone else tried using PASOE 11.7 with APSV session-free clients yet? The combination of those things should cause any open client application to crash after 30 mins. Apparently this is true for both Java and .Net open clients. I was pretty surprised when I first noticed it. I opened a support ticket with Progress and they created the following KB for the issue. Progress KB - PASOE failures after a period of inactivity . Most of my questions about this are answered; but the thing that still confuses me is why I encountered this so early in my PASOE evaluation which started a few months ago. I would not have expected that I would be the first on OE 11.7.2, nor the first to use the APSV transport. Note that in OE 11.7, the APSV transport now integrates with tomcat HTTP sessions by default. As I learned the hard way, APSV openclients will crash after being idle for 30 mins. The reason it takes 30 mins is because that is the default timeout for tomcat's HTTP sessions. And the APSV transport will now rely on tomcat's HTTP sessions while communicating with remote clients. So after exactly 30 mins, any expired session that you may attempt to use will likely cause your app to crash. This is the case for all sessions that are found in the session-free session pool; they will all become invalidated and, the next time you attempt to call an appserver method using the openclient connection, the application will crash. My theory is that there aren't many other customers who use OE version 11.7 in production yet, since it is less than a year old. Based on what tech support has told me, this issue should not affect customers on OE 11.6. For customers that plan on upgrading to OE 11.7 you may want to test your APSV applications and see how they behave after tomcat session expiration (which is 30 mins by default).
Continue reading...
Continue reading...