RDB - Clocks CPU at 100% Utilization [message #125537] |
Mon, 25 July 2005 15:11 ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: nospam.eclipse.org
Eclipse 3.1f + webtools 0.7 RC3 & RC1
Has anyone else experienced where you type a second SQL select statement
two lines down in the SQL scrapbook file, executed the query, watch the
previous results columns visually slowly disappear, then get clocked 100%
on CPU?
|
|
|
Re: RDB - Clocks CPU at 100% Utilization [message #125817 is a reply to message #125537] |
Tue, 26 July 2005 14:00 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: nospam.eclipse.org
Wrote a follow up as I've found the cause of the problem...this will
affect RDB's ability to connect to a variety of databases and is not
exclusive to DB2.
I was attempting to connect to a DB2 7.1 for OS / 390. I attempted using
every given combination of the DB2 JDBC drivers
COM.ibm.db2.jdbc.app.DB2Driver & COM.ibm.db2.jdbc.net.DB2Driver + all of
the given DB2 drivers in RDB: UDB, iSeries, zSeries, 7.0, 8.0, & 8.1.
While using the COM.ibm.db2.jdbc.app.DB2Driver driver, I was consistently
able to run the first query I typed in a .sqlpage file. The 2nd query
would always cause Eclipse to max out CPU utilization to 100%.
I installed the DBEdit Eclipse plug-in as a sanity check, and found that
the same behavior occurred with the DBEdit: the 2nd query would cause
Eclipse to max out CPU utilization to 100%. I fiddled around with the
connection settings in DBEdit, and found the culprit: the checkbox "Enable
scrollable result sets". The RDB & DBEdit plug ins were having problems
because they were trying to create bi-direction scrollable ResultSet
objects when the Connection (JDBC driver, or Database) doesn't support
scrollable type ResultSet objects.
I wonder if webtool's RDB is dependant on always having a bi-directional
scrollable ResultSet, and therefore does not support / give driver setups
to connect to any database that does not support scrollable result sets?
That would explain why the DB2 7.1 driver was dropped after webtools
milestone build #2.
|
|
|
Powered by
FUDForum. Page generated in 0.04394 seconds