Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#732 closed enhancement (fixed)

MetadataNotifier keep one active DB connection

Reported by: fxp Owned by: geonetwork-devel@…
Priority: minor Milestone: v2.7.0
Component: General Version:
Keywords: Cc:

Description

While settings the maxIdle parameter to 0 in the pool configuration, user can find a permanent IDLE in transaction connection to the DB.

Looking at the relation used in the DB, we can notice that one connection is always used by the MetadataNotifier due to openDirect call:

dbms = (Dbms) srvContext.getResourceManager().openDirect(Geonet.Res.MAIN_DB);

which pass the dbms to the metadata notifier threads and keep it until GeoNetwork stops (MetadataNotifierControl shutdown).

We could probably only open a db connection while the MetadataNotifierTask looks for changes to notify.

Change History (2)

comment:1 by fxp, 13 years ago

Resolution: fixed
Status: newclosed

Committed revision 8578.

comment:2 by ianwallen, 12 years ago

Milestone: Future releasev2.7.0
Note: See TracTickets for help on using tickets.