Shawn McKee <[EMAIL PROTECTED]> wrote:
This might explain why the Oracle thin client seems to solve the problem
too. There is no setting in that interface for the this value so my
assumption is that the thin client gets the information from the DB which
means there would never be a mismatch.
Wow two solutions for the same problem ;-)
Shawn
-----Original Message-----
From: Suzanne Capener-Byington [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 4:32 PM
To: CF-Server
Subject: Re: Cursor errors
We found the cause of the max open cursors exceeded error.
Our server admin Vernon Crandall verified that the cause of this is the max
pooled statements setting in CF Admin being set higher than the max number
of cursors in oracle. So just set your max pooled statements to something
lower than what our max cursor setting is for you oracle DB and the problem
is solved. We reconfirmed it. This is the definitive answer. And it
totally makes sense.
We were not getting this issue on CFMX 6.0 due to 6.0 being so much slower
on JBOSS/Tomcat configuration.
Suzanne Capener-Byington <[EMAIL PROTECTED]> wrote:
We are having the same issue. Never saw this on MX 6.0 but we see it very
frequently on 6.1. We haven't figured out what is causing it.
Joe Eugene <[EMAIL PROTECTED]> wrote:
I would always suggest you go with Vendor Provided JDBC Drivers. IF the
Vendor(Oracle) provides
Drivers for their Product, you should always go with these drivers.
Note: Since you have already created the Tables with the MM Drivers... No
need to do this again, if you
are going to use Oracle JDBC Drivers. This should solve the problem.
Also, you can always create an SP/JOB to purge out the data, rather than
have the application server do it.
I havent tested this, but should work fine.
Joe Eugene
----- Original Message -----
From: Shawn McKee
To: CF-Server
Sent: Monday, November 10, 2003 3:07 PM
Subject: Cursor errors
Testing MX upgrade and we are getting a lot of these.
[Macromedia][Oracle JDBC Driver][Oracle]ORA-00604: error occurred at
recursive SQL level 1 ORA-01000: maximum open cursors exceeded
Our DBA is asking about this query that he is finding in his logs.
SELECT cglobal.cfid
FROM cglobal
WHERE cglobal.lvisit < :v0
Clearly this is something the server is doing. Getting ready to clear
expired client variables? Incorrectly our MX server was set to do this as
is the CF5 server. We are resetting the MX server to not do that against
this database for now. Later we will reverse the situation. Is this the
likely culprit?
Thanks,
Shawn McKee
Manager, Web Development
NewsStand, Inc.
8620 Burnet Rd., Suite 400
Austin, TX 78757 USA
512-334-5100
NewsStand Inc. is the leader in digital delivery of newspapers, magazines
and other print publications. Our user-friendly technology and innovative
media distribution is changing the way people read. Now, we have over 50
titles (in several languages) for purchase as either single copies or
subscriptions that can be easily downloaded on your desktop, laptop or
Tablet PC. Here is a link to a free copy of The New York Times for you to
try. Select "Try a free sample" and click on "Add to cart."
http://newsstand.com/?fuseaction=signup
<http://newsstand.com/?fuseaction=signup>
<http://newsstand.com/?fuseaction=signup&promo_id=2295> &promo_id=2295
---------------------------------
---------------------------------
_____
---------------------------------
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
