Hi, I think I know what's going on. The pre-generalized data store is used there to have multiple generalized tables behind a single layer. The store uses Repository to fetch the original stores and features sources... which per se is not bad, but it ends up holding on to them, which is bad instead. The ResourcePool under pressure, or due to re-configuration, can dispose of the store instances and create new ones, and then the pre-generalized store ends up having dangling objects which throw that exception.
The work-around is to call "reset" after config changes. The fix is to go into the pre-generalized store and make it stop holding references, and call onto the Repository every time it needs a FeatureSource. A bug report is welcomed, an actual fix much more so. Cheers Andrea On Wed, Mar 10, 2021 at 3:33 PM Jody Garnett <jody.garn...@gmail.com> wrote: > Ashley: > > You are the first person to report this error (although I suspect others > may of also seen it and assumed someone else has reported). > > Can I ask for some more detail? There should be a stack tract in the logs > associated with this error; it may give us a clue which DataSource is > causing problems. > > The changing the database connection parametes is a good clue! I may > expect a problem for rendering that occurs *right when* the connection is > interrupted. > > Jody > > On Tue, Mar 9, 2021 at 5:22 PM Ashley Mort via Geoserver-users < > geoserver-users@lists.sourceforge.net> wrote: > >> I am getting: >> code=”internalError”Rendering process failed >> >> DataSource not available after calling dispose() or before being set. >> >> >> >> I am on GeoServer 2.17.2 on RedHat and using Andrea’s workspace from the >> osm-styles repo and connecting to a PostGIS DataStore which I loaded with >> some OSM data via imposm. >> >> >> >> I get this error somewhat randomly and if I restart GeoServer, it seems >> to stop happening for a while but will eventually come back (even when >> making the exact same WMS request for an exact / known area that worked >> earlier). >> >> >> >> Is this something that may be fixed in a later version of GeoServer? >> Does it have something to do with the speed of the connection to my >> DataStore? Any tips would be appreciated as this is a tough one for me. >> Thank you! >> >> >> >> >> >> PS: If I re-enter my DataStore passwd and Save, that seems like it may >> trigger the error on subsequent requests. >> >> >> >> >> >> >> >> Ashley Mort >> >> Sr. Software Engineer >> >> 972-638-6317 office >> >> 814-571-3039 cell >> _______________________________________________ >> 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 >> > -- > -- > Jody Garnett > _______________________________________________ > 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 > -- Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- *Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.*
_______________________________________________ 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
