D
dbeavon
Guest
Manfred, I don't seem to be having issues with session-managed connections. They typically connect from scratch every time, allocating brand new resources and freeing them up when the connection is closed. It is "session free" connections that seem more challenging because they are designed to hold on to resources for an extended period. (I believe that a "pool" of available sessions in the client is linked to a corresponding set of tomcat sessions on the server). This advanced "session free" connection management/pooling seems to work less well in PASOE than in the "classic appserver". It is perfectly understandable that the PASOE server would want to clean up its resources after a half an hour of inactivity. The problem is that the .Net open client is not able to react properly when it tries to re-use an outdated session - from the pool - that the tomcat server has already purged from memory. Ideally it would automatically allocate new server-side resources if needed.
Continue reading...
Continue reading...