D
dbeavon
Guest
If anyone has expertise on PASOE and its integration with tomcat, I have a fairly technical question. Should I be cautious of any solution that tells me to *remove* the tomcat timeouts altogether (ie. no session timeouts)? It seems like a dangerous workaround. When I've tested it, I discover that PASOE clients (APSV transport) will often have sessions left open in the list of tomcat sessions indefinitely. (This can be easily seen in the tomcat manager webapp). This is especially true for "session-free" clients. The tomcat sessions, once opened, will *never* be terminated from the server side of things, except when manual/administrative operations are performed (eg. restarting the tomcat instance). They continue to remain in memory long after client application processes have been shut down (gracefully or otherwise). We are running 11.7.2. Here is an example of a kb that seems to indicate that we should remove tomcat session timeouts: Progress KB - Changing idle session timeout option has no effect in PASOE ie. this could be done by changing the web xml configuration as follows: -1 We've been having troubles with the default tomcat session timeout (30 mins), especially as it relates to "session-free" APSV clients. But I think if the "solution" is to remove session timeouts altogether, then that cure may be worse than the original problem. I wanted to get some input regarding whether it is appropriate to remove session timeouts. I was surprised that was even mentioned in the OE KB.
Continue reading...
Continue reading...