Hi All,
I have done a fair amount of testing on this, and am pretty sure it is a bug introduced between beta3 and RC1 – but am not sure if it is in the GS or GT domain.
When starting up GeoServer, OC4J reports the following:
2011-01-26 17:15:02.999 WARNING J2EE DS-00265 Unclosed connection detected : ‘oracle.oc4j.sql.spi.ConnectionFinalizer@anonymised.com.’ : ‘’.
2011-01-26 17:15:03.003 WARNING J2EE DS-00265 Unclosed connection detected : ‘oracle.oc4j.sql.spi.ConnectionFinalizer@anonymised.com.’ : ‘’.
2011-01-26 17:15:03.004 WARNING J2EE DS-00265 Unclosed connection detected : ‘oracle.oc4j.sql.spi.ConnectionFinalizer@anonymised.com.’ : ‘’.
2011-01-26 17:15:03.005 WARNING J2EE DS-00265 Unclosed connection detected : ‘oracle.oc4j.sql.spi.ConnectionFinalizer@anonymised.com.’ : ‘’.
2011-01-26 17:15:03.239 WARNING J2EE DS-00265 Unclosed connection detected : ‘oracle.oc4j.sql.spi.ConnectionFinalizer@anonymised.com.’ : ‘’.
2011-01-26 17:15:03.240 WARNING J2EE DS-00265 Unclosed connection detected : ‘oracle.oc4j.sql.spi.ConnectionFinalizer@anonymised.com.’ : ‘’.
2011-01-26 17:15:03.240 WARNING J2EE DS-00265 Unclosed connection detected : ‘oracle.oc4j.sql.spi.ConnectionFinalizer@anonymised.com.’ : ‘’.
2011-01-26 17:15:03.242 WARNING J2EE DS-00265 Unclosed connection detected : ‘oracle.oc4j.sql.spi.ConnectionFinalizer@anonymised.com.’ : ‘’.
2011-01-26 17:15:03.242 WARNING J2EE DS-00265 Unclosed connection detected : ‘oracle.oc4j.sql.spi.ConnectionFinalizer@anonymised.com.’ : ‘’.
2011-01-26 17:15:03.243 WARNING J2EE DS-00265 Unclosed connection detected : ‘oracle.oc4j.sql.spi.ConnectionFinalizer@anonymised.com.’ : ‘’.
2011-01-26 17:15:03.244 WARNING J2EE DS-00265 Unclosed connection detected : ‘oracle.oc4j.sql.spi.ConnectionFinalizer@anonymised.com.’ : ‘’.
Which is the number of coverages configured on my dev system.
I am using a custom GeoRaster Plugin (which I know is unsupported), but this worked fine in versions previous to RC1.
I have gone through the code to the custom plugin, and can confirm that ALL connections are being closed – it seems this only occurs when Geoserver first starts up, so whatever reads the workspace configurations, and calling the database is keeping them open. To confirm this, I place logging information in my getConnection and closeConnection methods, none of which appear in the startup log, but appear when I access my data, leading me to believe even more that this is not plugin related. My vector data is fine (using the Oracle NG datastore) it is just my raster data.
Again, this does seem trivial seeing as the connection pool is configured to remove unused connections after x amount of time, but this shuld be happening gracefully within the code.
I can confirm that this only happened since RC1 was released.
Any thought anyone?
Kind Regards,
Steve