Opened 13 years ago
Closed 12 years ago
#555 closed defect (fixed)
spatial index writer code has long running transaction vulnerable to db connection problems
| Reported by: | simonp | Owned by: | jesseeichar |
|---|---|---|---|
| Priority: | major | Milestone: | v2.7.0 |
| Component: | General | Version: | v2.6.4 |
| Keywords: | Cc: | darb1@… |
Description
SpatialIndexWriter (which uses a geotools datastore plus connection pool) has long running transaction which doesn't recover gracefully from connection loss.
Switching to autocommit doesn't seem to affect performance negatively even when loading large sets of records.
Change History (4)
comment:1 by , 12 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 12 years ago
comment:3 by , 12 years ago
I have looked at the documentation you have added and it seems that the issue should be just fine. Do we still need to do anything else?
comment:4 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Hi Jesse - no more to add as I think its ok now that we have changed the database pool (using apache dbcp or JNDI) so can be closed as fixed. Thanks.
Note:
See TracTickets
for help on using tickets.
Hi Simon,
I have made a change so that if the MaxWrite < 2 then there will be no transaction. Do you think that is sufficient? Perhaps I should make the default value == 1 as well?
Jesse