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

Nathan Andelin skrev:

Oh well, at least is sounds like Richard, Aaron, and even Thorbjørn have in one case or another maintained database connections by individual session.

Well, I'm fine with being in such fine company :)

I have in the last few months been the user of a high -profile, high-traffic web site, which was rewritten which had been a long time underway. I don't know the details but let it suffice to say that it looked very pretty but couldn't handle real life trafic and I could see that it was database connection pool timeouts (so they didn't stress test, whee). Even now months later, it cannot handle high loads properly. Essentially I'd like to avoid a similar situation where I'm responsible, so it is nice to know which factors to look out for first, and how people have solved these things in general.

If there are no immediate brickwalls ahead in the planned scenario, then keep it simple. I.e. a connection per user. It is also much easier to handle library lists etc, when you don't have to deal with reusing connections. I looked at the pooling (must have been for the generic AS400 connectino) in the toolbox, and it allows for pooling on user/host, but not any finer than that. In other words, you cannot have a generic connection pool where the same user may use different applications with different library lists, so you need to do something else, and it is written in a way that makes it rather difficult to subclass. It is much easier to pool and otherwise manipulate JDBC connections :)

Anyone who have successfully debugged a stored procedure? I saw some properties to set but was in a hurry, and just recalled that I had a MCH1202 the other day I had to manually tickle the waiting job to get back to the caller.
/Thorbjørn