On Sun, Apr 12, 2015 at 3:16 AM, Andrea Aime <[email protected]>
wrote:
> We are running production setups with more complex situations (more
> mosaics, more traffic), so I guess we need to figure out what's making
> yours different... I guess it's the lack of JNDI usage, we only do
> production setups with JNDI because normally we have many mosaics
> (and if we don't, each mosaic would have its own private pool).
>
My plan was to switch to JNDI, but was just doing non-JNDI in development
and experienced this. I have switched to JNDI and am experiencing a
different issue, and am e-mailing about that in a different thread. Even
if I switch to JNDI, this issue would remain for those who don't.
> From what I see, assuming GeoServer is the only application that can chew
> away connections, we are probably leaking pools... are you calling
> reloads in your scripts?
>
Yes, GeoServer is the only application running that can chew away at
connections. As far as reloads in the script, do you mean catalog
reloads? Just whatever gsconfig does when you save a resource. HOWEVER,
please see the part of my e-mail where I tested this with curl from the
command line completely outside of my script. There was certainly no
reload there. Just one REST command issued ... and a new database
connection established by GeoServer every time I ran that command.
Thanks,
Mike
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
