GeoTools

ComplexDataStore not disposing JDBC connections

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.4.2
  • Fix Version/s: 2.4.5
  • Component/s: app-schema plugin
  • Labels:
    None

Description

Users encounter runtime errors indicating JDBC connections are not disposed.

GroupingFeatureIterator3 contains logic to use sneaky iteration tricks to dispose the underlying simple DataStores. DefaultMappingFeatureIterator does not. The latter is used when the mapping contains an empty groupBy. The solution might be to pull up the Iterable implementation into the common base class AbstractMappingFeatureIterator.

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. GEOS-1903 ClassCast Exception after restarting geoserver using the community schema

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ben Caradoc-Davies added a comment -
Nothing to do with GroupingFeatureIterator3. Problem was FeatureAccessFactoryAdapter.canAccess not disposing of temporary DataStore.
Show
Ben Caradoc-Davies added a comment - Nothing to do with GroupingFeatureIterator3. Problem was FeatureAccessFactoryAdapter.canAccess not disposing of temporary DataStore.
Hide
Permalink
Andrea Aime added a comment -
Mass closing all issues that have been in "resolved" state for 2 months or more without any feedback or update
Show
Andrea Aime added a comment - Mass closing all issues that have been in "resolved" state for 2 months or more without any feedback or update

People

  • Assignee:
    Ben Caradoc-Davies
    Reporter:
    Ben Caradoc-Davies
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: