On Thu, 10 Jan 2019 at 09:14, Paul Wittle <p.wit...@dorsetcc.gov.uk> wrote:
> Thanks Ian, > > > > That is really helpful to know. Should the documentation be telling users > to install the JTDS jar instead of the Microsoft one then? Another good one > for me to have a go at perhaps I feel like I should be able to manage a > pull request for the documentation? > It might be worth adding that. > > Do you think the prevent memory leaks message is unlikely to be linked and > has anyone else started getting these appearing recently? > > I doubt that they are or that those messages are important (if there was a major memory leak we would probably have spotted it by now). Ian > > > Thanks, > > Paul > > > > *From:* Ian Turton <ijtur...@gmail.com> > *Sent:* 10 January 2019 08:17 > *To:* Paul Wittle <p.wit...@dorsetcc.gov.uk> > *Cc:* geoserver-users@lists.sourceforge.net > *Subject:* Re: [Geoserver-users] Memory leak error messages > > > > The JTDS driver was added to the MS SQL GeoTools module some time ago > (version 14.x) but if it is not present the slower MicroSoft driver will be > used. See > http://docs.geotools.org/latest/userguide/library/jdbc/sqlserver.html for > more information. > > > > Ian > > > > On Wed, 9 Jan 2019 at 18:22, Paul Wittle via Geoserver-users < > geoserver-users@lists.sourceforge.net> wrote: > > Hi, > > > > Quick update to my own post. Using developer logging I was getting > messages about JTDS not being present in the classpath. This confused me as > there is no reference to JTDS at all that I could find but I did add the > jar file to see what happened. With it present I find that the error in the > original email is often associated as follows (in terms of timing) but I > couldn’t say if there is an actual link. > > > > 2019-01-09 14:09:39,817 TRACE [geotools.factory] - RETURN > (GridCoverageFactory): found implementation Optional. > > 2019-01-09 14:09:39,817 TRACE [geotools.factory] - ENTRY > (GridCoverageFactory) > > 2019-01-09 14:09:39,817 TRACE [geotools.factory] - RETURN > (GridCoverageFactory): found implementation Optional. > > 2019-01-09 14:09:39,817 DEBUG [sqlserver.jtds] - Target not a string > > 2019-01-09 14:09:39,817 ERROR [geotools.map] - Call MapContent dispose() > to prevent memory leaks > > > > I notice that JTDS debug messages are starting to appear in other people’s > error log’s when searching for previous questions. Is JTDS support > something that has been added on purpose or have I just managed to > misconfigure something? > > > > I do have the Microsoft SQL Server and SQL Azure extension installed and > this is the only place that I can find JTDS listed. > > > > Searching the Geoserver code base this is the only reference to JTDS I’ve > found: > > > https://github.com/geoserver/geoserver/blob/445625cdad44e79c48682b0c9852e1e2586c018e/src/community/release/ext-wps-remote.xml > > > > That is not currently installed but I may have installed it on DEV > previously so perhaps that plugin has introduced something into my > configuration? > > > > Thanks, > > Paul > > > > *From:* Paul Wittle > *Sent:* 09 January 2019 13:53 > *To:* 'geoserver-users@lists.sourceforge.net' < > geoserver-users@lists.sourceforge.net> > *Subject:* Memory leak error messages > > > > Hi, > > > > I’ve recently updated us to the latest version of GeoServer (stable) and > I’ve started getting a lot of these errors: > > > > 2019-01-09 13:50:49,127 ERROR [geotools.map] - Call MapContent dispose() > to prevent memory leaks > > > > Does anyone know which logging profile I need to get a more informative > message about the cause of this error? > > > > Best Regards, > > > > Paul Wittle > > GIS Developer > > Insight, Intelligence & Performance > > > > County Hall > > Dorchester > > Dorset. DT1 1XJ > > Tel: 01305 228473 > > E mail: p.wit...@dorsetcc.gov.uk > > > > "This e-mail is intended for the named addressee(s) only and may contain > information about individuals or other sensitive information and should be > handled accordingly. Unless you are the named addressee (or authorised to > receive it for the addressee) you may not copy or use it, or disclose it to > anyone else. If you have received this email in error, kindly disregard the > content of the message and notify the sender immediately. Please be aware > that all email may be subject to recording and/or monitoring in accordance > with relevant legislation." > > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > > > > > -- > > Ian Turton > "This e-mail is intended for the named addressee(s) only and may contain > information about individuals or other sensitive information and should be > handled accordingly. Unless you are the named addressee (or authorised to > receive it for the addressee) you may not copy or use it, or disclose it to > anyone else. If you have received this email in error, kindly disregard the > content of the message and notify the sender immediately. Please be aware > that all email may be subject to recording and/or monitoring in accordance > with relevant legislation." > -- Ian Turton
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
