D
dbeavon
Guest
There is a KB about using -1 in pasoe: knowledgebase.progress.com/.../Changing-idle-session-timeout-option-has-no-effect-in-PASOE I'm curious what type of client you are using? And what the failure message looks like from the client side of things? We used an openclient (.net) and the failure was hard to track down. That was mainly because the exception message that surfaced in the client process was extremely generic and unhelpful, with no inner exceptions ("Communication layer message: General Error. 9998"). It sounds like you are already way beyond that part of the troubleshooting. In any case, if your problems are related to the .net or java openclients, there is a kb for that too: knowledgebase.progress.com/.../pasoe-failures-after-a-period-of-inactivity We went with workaround #2 and used a very high timeout (1 or 2 days). I think the tomcat process can handle an extremely high number of active sessions, so your timeout can be quite high. I don't know that I would make it *infinite* unless you are also restarting tomcat on a weekly basis...
Continue reading...
Continue reading...