Lars, Apparently I misspoke. I have been using the original jrun_drivers.jar supplied with JRun 3.1 successfully with their custom tags against SQL Server 2000 for selects, inserts, and deletes. My co-worker had been using the Oracle classes12.zip library to do selects against Oracle 8i running on Solaris. But he got the same error you mention - OutOfMemoryError, when attempting an insert. So you are right. The only driver/database combination we've had complete success with using JRun Custom Tags (so far) is the previous jrun_drivers.jar connecting to SQL Server.
Thanks for revealing this problem. I'm now wondering if I'm wasting my time using JRun's Custom Tag Library. Hopefully the Allaire/Macromedia's statement that a patch "will be released soon" is accurate... .Randy -----Original Message----- From: lars [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 25, 2001 12:02 PM To: JRun-Talk Subject: JDBC drivers, JRun custom tags, bugs (was IIS 4 dies, no memory leak: NT4SP6 + JRun 3.0) Randy: Yes, the bug absolutely is driver-dependant -- when I prototyped my database queries using JRun 3.1, its taglib and a MS SQL Server 7 db (via the driver in jrun_drivers.jar) I saw nothing of the behaviour related to bug #26844. Unfortunately 3rd-party driver choices seem to be very limited for the installation at hand: our customer uses Oracle 7 on an Origin 2000 server; its OS is IRIX and there is no upgrade path available for this project. The beauty (from my point of view) of the Oracle thin driver on our JRun server (NT4 box) is that it communicates fine with the older Oracle version and required no additional resources be installed on the Origin 2000 server (which hosts a lot of stuff and has few resources to spare). I'm intrigued that you accessed Oracle using type 4 drivers and the JRun custom tags. Could you specify your server OS, which drivers, etc.? Anyway, we're creeping way off topic here -- I started this new thread if you'd like to continue discussion of the JRun custom tags and access to db's. -- Lars Laurence Middleton code wrangler ecentricarts inc. 416 644-5000 ext.225 > -----Original Message----- > From: Fishwick, Randall [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 25, 2001 12:30 PM > To: JRun-Talk > Subject: RE: IIS 4 dies, no memory leak: NT4SP6 + JRun 3.0 > > > Lars, > > It appears bug #26844 is related to the supplied JDBC drivers in > jrun_drivers.jar. I was getting the following error using the updated > jrun_drivers.jar to access SQL Server 2000: "The cursor identifier value > provided (abcdef0) is not valid.", and Allaire's response is: > "This problem > is logged as a bug # 27241. Please refer to next fix and use any > other third > party JDBC driver for this CMP implementation till that time." > We have been > using Oracle's Type 4 drivers to access Oracle without problems using the > JRun Custom Tag Library. Additionally, I am using the original > jrun_drivers.jar supplied with JRun 3.1 to access SQL Server with the Tag > Library without a problem. So I'm wondering if using good third > party JDBC > drivers would eliminate bug > #26844? > > .Randy > > -----Original Message----- > From: lars [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 25, 2001 7:35 AM > To: JRun-Talk > Subject: RE: IIS 4 dies, no memory leak: NT4SP6 + JRun 3.0 > > > Randall: > > This is a documented (but as-yet unaddressed) bug with the > Allaire/Macromedia folks, #26844 according to the JRun forums. > > Allaire JRun forum links: > http://forums.allaire.com/jrun/messageview.cfm?catid=69&threadid=208338 is > the first mention of the bug report -- sadly for us, Allaire/Macromedia > doesn't publish their bug lists, but no doubt they have their reasons. > http://forums.allaire.com/jrun/messageview.cfm?catid=66&threadid=227136 > promises a fix "will be released soon" (as of Oct.23rd). > > Searching the JRun forums for the bug number or > "java.lang.OutOfMemoryError" > will turn up more references. > > Also, I started a thread in this list September 13, asking whether anyone > had tried using JRun 3.1 with the custom tag library from JRun 3.0 (the > Allaire/Macromedia engineers said it was a bad idea). > > The bug affects only use of the custom tag library for SQL queries -- I > presume you're connecting & doing your queries via the usual Java classes. > > Laurence Middleton > code wrangler > ecentricarts inc. > 416 644-5000 ext.225 > > > > -----Original Message----- > > From: Fishwick, Randall [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, October 23, 2001 2:27 PM > > To: JRun-Talk > > Subject: RE: IIS 4 dies, no memory leak: NT4SP6 + JRun 3.0 > > > > > > Lars, > > > > Your background info indicates a "known issue" regarding > INSERT & UPDATE > > queries using classes12.zip, but we've been running IIS 4 and 5 with 3.1 > > JRun using that Oracle JDBC driver for a while without any > problems doing > > inserts or updates. Where is the problem documented? > > > > Thanks, > > Randy [...] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/jrun-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
