I agree, that is how I would expect it to work. But alas it doesn't.
For example a page with 2 procedure calls = two oracle sessions. So
rather than base it on request or whatnot, we open a connection
(through our java api) per user and maintain one single session per
user. If a procedure hasn't been called in the specified 'session
timeout' then we kill the session.
Although now that I think about, I think we are talking about two
things... database sessions and connections. Or are we?
-Adam
----- Original Message -----
From: Jochem van Dieten <[EMAIL PROTECTED]>
Date: Wed, 23 Jun 2004 21:15:08 +0200
Subject: Re: Understanding/Defending Coldfusion connections
To: CF-Talk <[EMAIL PROTECTED]>
Adrocknaphobia wrote:
> Actually, the option to maintain database connections doesnt seem to
> really work (for J2EE ---> Oracle).
It does for PostgreSQL. Even the bug where the configured maximum
number of connections was not actually enforced has been fixed in
6.1.
Jochem________________________________
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
