I've got to disagree with you there... I think using a good IDE with proper debugging is the BEST way to go, but it's certainly not the SIMPLEST way to go. Don't get me wrong, I'm all for using a debugger and I think folks should have one set up as part of their development environment, but often times it's not trivial to set one up. And if you're under the gun to solve a critical problem (and didn't have a deugger set up), I would:
1. kick myself for not having installed/configured my debugger earlier 2. fix the immediate problem at hand using the most efficient method possible 3. set up my development environment properly for the future I'm also a big fan of debugging output combined with an efficient logging strategy. If you run into a problem with a production system, a detailed audit log can be a lifesaver. Just my $.02 Kristian -----Original Message----- From: Tormod Hystad [mailto:[EMAIL PROTECTED]] Sent: Friday, December 21, 2001 4:57 AM To: JRun-Talk Subject: RE: Transaction Problem That's not the simplest way... The simplest way is to set up proper debugging with a good IDE against your JRun server and step through the code, line-by-line and see what's causing the problem. See: http://www.allaire.com/Handlers/index.cfm?ID=22271&Method=Full for Forte 3.0 info http://www.allaire.com/Handlers/index.cfm?ID=21913&Method=Full for JBuilder 5 info http://www.allaire.com/Handlers/index.cfm?ID=20830&Method=Full for JBuilder 4 info http://www.allaire.com/Handlers/index.cfm?ID=14529&Method=Full for other IDE's This is really a must for efficient developing/debugging. - Tormod -----Original Message----- From: Kristian Cibulskis [mailto:[EMAIL PROTECTED]] Sent: 21. desember 2001 00:14 To: JRun-Talk Subject: RE: Transaction Problem Do you know _exactly_ what line is causing the exception to be thrown? The simplest way to do this is to put debugging output around each line and then see what is output before the error. Each of the below lines could be causing the ultimate exception, but the reason WHY they would be throwing that exception is very different for each. Once you know the line, post it up here. Kristian PS - I'm assuming that you have obtained PreparedStatement1 and PreparedStatement2 from the associated connection, and not some other connection object... but it wasn't clear from the code snippet. Is that true? -----Original Message----- From: Sergio Moreno [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 2:12 PM To: JRun-Talk Subject: Transaction Problem Hi: Does anybody know what is the mistake here? i'm using the Connection object to start a transaction using : [conection_name].commit(); [conection_name].setAutoCommit(false); try { . PreparedStatement1.executeUpdate(); PreparedStatement2.executeUpdate(); [conection_name].commit(); . } catch (SQLException e) { [conection_name].rollback(); } then shows the error "Invalid Cursor State" by the way the driver is com.ibm.as400.access.AS400JDBCDriver and i use the datasource model to obtain the connecction Sergio Moreno V. AFP PREVISION * BBV ______________________________________________________________________ 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/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
