Re: [udig-users] Connection is closed on line editing and committing

[Jody Garnett <jody.garnett@xxxxxxxxx>]

I discovered a problem in uDig 1.3.2: It occurs when drawing lines using the standard line drawing tool and committing as soon as drawing is finished (by hitting the commit button immediately after [enter] or double clicking). If the described procedure is done multiple times, I get a connection is closed exception before the fifth iteration. Something (renderer) called a connection.close() (on the dbcp connection wrapper) on the EditManager-transaction-connection. After the connection was closed, no more lines can be drawn.

I seem to recall running into this and fixing it last year.

I am using an Oracle database connection (on a win32 system), although I don’t think, after debugging, that it has anything to do with it.

 

I cannot confirm if this error still exists in uDig 1.4.0, because I after adding an oracle spatial geometry layer, the renderer.draw() just gives me a lot of null pointer exceptions.

Would be interested to know the stack trace of that, I cannot remember the differences between 1.3.2 and 1.4.0. 

Main cause of the use of uDig, mentioned above, is to have every change safely committed to the database (not relying on the reliability of the program). Is there any other method (like turning auto commit on for the edit connection)? Can the connection somehow be recovered in that scenario, like by reinitializing the transaction? Has somebody an idea, how the problem can be fixed?

I had not considered making an "auto commit" mode, mostly as with shape files that involves writing out the entire shapefile each time.

 

However one thing you can do is go to the catalog, right click, and "reset" the database. This will recreate it with a new connection pool.