Re: Persistent Sessions in DB connection for QZDASOINIT, implemented by Nathan

Nathan Andelin skrev:

They were using standard JDBC connections, which activated QZADASOINIT prestart jobs for each open connection. Rather than sharing that connection with multiple users, each user was provided their own connection, so that the state of SQL result sets in QZDASOINIT jobs were preserved from one request to the next, for each user. My colleages wrote a "connection manager" class for managing the connections. But the jist of it was that each individual user had their own connection, which remained opened and dedicated to that individual until an "Exit" link was clicked, or a period of inactivity had elapsed.

I did the same for another web application as discussed earlier as we did not see any issues with the loads we were dealing with for this application. Most likely you and your java colleagues have had many more users than we did. I was wondering if you had any experiences to share (except the one I would like to hear - namely that the autoadjustment of OS/400 coped well with all stress situations :)

/Thorbjørn