[Geoserver-users] REST Ingestion and Database - Too many clients

GeoServer GeoServer User
1

Dear all,

I am running geoserver 2.7.0 on a Ubuntu 14.04.

I am using the REST interface to append images to a mosaic time series. That works fine. But some things happen in the logfiles which I cannot explain.

May be you can give me an advice, what I can improve, to solve some of the below mentioned log messages.

Here are the excerpts from the logfiles:

postgres logfile:
2015-04-28 12:28:56 CEST ERROR: stats for “my_layer.the_geom” do not exist
2015-04-28 12:28:56 CEST CONTEXT: SQL function “st_estimated_extent” statement 2
2015-04-28 12:28:56 CEST STATEMENT: select ST_AsText(ST_force_2d(ST_Envelope(ST_Estimated_Extent(‘public’, ‘my_layer’, ‘the_geom’))))

geoserver logfile:
2015-04-28 10:29:48,857 WARN [geotools.jdbc] - Failed to use ST_Estimated_Extent, falling back on envelope aggregation
org.postgresql.util.PSQLException: ERROR: stats for “my_layer.the_geom” do not exist
Wobei: SQL function “st_estimated_extent” statement 2
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)

description=Features from JDBCDataStore
2015-04-28 10:33:52,648 WARN [imagemosaic.catalog] - This granule catalog was not properly dispose as it still points to: ServiceInfo
description=Features from JDBCDataStore

Is that connected with this:
http://docs.geoserver.org/stable/en/user/data/database/primarykey.html

After many ingestions, I also get this message in the postgres log:
2015-04-27 18:48:04 CEST FATAL: sorry, too many clients already

Thank you for any suggestions.

Christoph

2

Christoph,

Are you using JNDI or just directly setting your database settings in the datastore.properties file? I ask this because I was seeing what looked like a connection starvation / connection leak issue harvesting image mosaic granules without using JNDI. Your “too many clients already” error makes me wonder if you are seeing a similar issue.

  • Mike
···

On Tue, Apr 28, 2015 at 6:59 AM, Christoph Kleih <me@anonymised.com> wrote:

Dear all,

I am running geoserver 2.7.0 on a Ubuntu 14.04.

I am using the REST interface to append images to a mosaic time series. That works fine. But some things happen in the logfiles which I cannot explain.

May be you can give me an advice, what I can improve, to solve some of the below mentioned log messages.

Here are the excerpts from the logfiles:

postgres logfile:
2015-04-28 12:28:56 CEST ERROR: stats for “my_layer.the_geom” do not exist
2015-04-28 12:28:56 CEST CONTEXT: SQL function “st_estimated_extent” statement 2
2015-04-28 12:28:56 CEST STATEMENT: select ST_AsText(ST_force_2d(ST_Envelope(ST_Estimated_Extent(‘public’, ‘my_layer’, ‘the_geom’))))

geoserver logfile:
2015-04-28 10:29:48,857 WARN [geotools.jdbc] - Failed to use ST_Estimated_Extent, falling back on envelope aggregation
org.postgresql.util.PSQLException: ERROR: stats for “my_layer.the_geom” do not exist
Wobei: SQL function “st_estimated_extent” statement 2
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)

description=Features from JDBCDataStore
2015-04-28 10:33:52,648 WARN [imagemosaic.catalog] - This granule catalog was not properly dispose as it still points to: ServiceInfo
description=Features from JDBCDataStore

Is that connected with this:
http://docs.geoserver.org/stable/en/user/data/database/primarykey.html

After many ingestions, I also get this message in the postgres log:
2015-04-27 18:48:04 CEST FATAL: sorry, too many clients already

Thank you for any suggestions.

Christoph

One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

3

Dear Mike,

thank you for your response.
I am setting the database information in the datastore.properties file.
Does it make sense to switch to JNDI?
Can I still activate that?

Thank you,
Christoph

Am 29.04.2015 15:04, schrieb Mike Grogan:

Christoph,

Are you using JNDI or just directly setting your database settings in
the datastore.properties file? I ask this because I was seeing what
looked like a connection starvation / connection leak issue harvesting
image mosaic granules without using JNDI. Your "too many clients
already" error makes me wonder if you are seeing a similar issue.

- Mike

On Tue, Apr 28, 2015 at 6:59 AM, Christoph Kleih <me@anonymised.com
<mailto:me@anonymised.com>> wrote:

    Dear all,

    I am running geoserver 2.7.0 on a Ubuntu 14.04.

    I am using the REST interface to append images to a mosaic time
    series. That works fine. But some things happen in the logfiles
    which I cannot explain.

    May be you can give me an advice, what I can improve, to solve
    some of the below mentioned log messages.

    Here are the excerpts from the logfiles:

    postgres logfile:
    2015-04-28 12:28:56 CEST ERROR: stats for "my_layer.the_geom" do
    not exist
    2015-04-28 12:28:56 CEST CONTEXT: SQL function
    "st_estimated_extent" statement 2
    2015-04-28 12:28:56 CEST STATEMENT: select
    ST_AsText(ST_force_2d(ST_Envelope(ST_Estimated_Extent('public',
    'my_layer', 'the_geom'))))

    geoserver logfile:
    2015-04-28 10:29:48,857 WARN [geotools.jdbc] - Failed to use
    ST_Estimated_Extent, falling back on envelope aggregation
    org.postgresql.util.PSQLException: ERROR: stats for
    "my_layer.the_geom" do not exist
      Wobei: SQL function "st_estimated_extent" statement 2
        at
    org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)
       
     description=Features from JDBCDataStore
    2015-04-28 10:33:52,648 WARN [imagemosaic.catalog] - This granule
    catalog was not properly dispose as it still points to: ServiceInfo
     description=Features from JDBCDataStore

    Is that connected with this:
    http://docs.geoserver.org/stable/en/user/data/database/primarykey.html

    After many ingestions, I also get this message in the postgres log:
    2015-04-27 18:48:04 CEST FATAL: sorry, too many clients already

    Thank you for any suggestions.

    Christoph

    ------------------------------------------------------------------------------
    One dashboard for servers and applications across
    Physical-Virtual-Cloud
    Widest out-of-the-box monitoring support with 50+ applications
    Performance metrics, stats and reports that give you Actionable
    Insights
    Deep dive visibility with transaction tracing using APM Insight.
    http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
    _______________________________________________
    Geoserver-users mailing list
    Geoserver-users@lists.sourceforge.net
    <mailto:Geoserver-users@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/geoserver-users

4

Instructions can be found at: http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_datastore.html. See the JNDI section. One warning, I found that the minEvictableIdleTimeMillis and timeBetweenEvictionRunsMillis settings in the examples seemed to oddly cause me problems with stale database connections that didn’t seem to get validated before re-use.

Take a look at this user list conversation between Andrea and me: http://osgeo-org.1560.x6.nabble.com/postgres-connection-exhaustion-Image-Mosaic-Harvesting-td5200863.html

It discusses the connection exhaustion issue I was seeing when harvesting granules via REST and discusses transitioning to JNDI.

Before you switch to JNDI, I would be interested to see how many postgres connections you show with the psql command “select datid, datname, pid, client_addr, client_port, state, query from pg_stat_activity;.” Do your number of connections increase each time you harvest a granule? Just wondering if you are seeing the same thing as me. I should have opened a JIRA issue on this, but the transition to the new JIRA was ongoing and then I got lazy.

Thanks,

Mike Grogan

···

On Wed, Apr 29, 2015 at 9:09 AM, Christoph Kleih <me@anonymised.com048…> wrote:

Dear Mike,

thank you for your response.
I am setting the database information in the datastore.properties file. Does it make sense to switch to JNDI?
Can I still activate that?

Thank you,
Christoph

Am 29.04.2015 15:04, schrieb Mike Grogan:

Christoph,

Are you using JNDI or just directly setting your database settings in the datastore.properties file? I ask this because I was seeing what looked like a connection starvation / connection leak issue harvesting image mosaic granules without using JNDI. Your “too many clients already” error makes me wonder if you are seeing a similar issue.

  • Mike

On Tue, Apr 28, 2015 at 6:59 AM, Christoph Kleih <me@anonymised.com> wrote:

Dear all,

I am running geoserver 2.7.0 on a Ubuntu 14.04.

I am using the REST interface to append images to a mosaic time series. That works fine. But some things happen in the logfiles which I cannot explain.

May be you can give me an advice, what I can improve, to solve some of the below mentioned log messages.

Here are the excerpts from the logfiles:

postgres logfile:
2015-04-28 12:28:56 CEST ERROR: stats for “my_layer.the_geom” do not exist
2015-04-28 12:28:56 CEST CONTEXT: SQL function “st_estimated_extent” statement 2
2015-04-28 12:28:56 CEST STATEMENT: select ST_AsText(ST_force_2d(ST_Envelope(ST_Estimated_Extent(‘public’, ‘my_layer’, ‘the_geom’))))

geoserver logfile:
2015-04-28 10:29:48,857 WARN [geotools.jdbc] - Failed to use ST_Estimated_Extent, falling back on envelope aggregation
org.postgresql.util.PSQLException: ERROR: stats for “my_layer.the_geom” do not exist
Wobei: SQL function “st_estimated_extent” statement 2
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)

description=Features from JDBCDataStore
2015-04-28 10:33:52,648 WARN [imagemosaic.catalog] - This granule catalog was not properly dispose as it still points to: ServiceInfo
description=Features from JDBCDataStore

Is that connected with this:
http://docs.geoserver.org/stable/en/user/data/database/primarykey.html

After many ingestions, I also get this message in the postgres log:
2015-04-27 18:48:04 CEST FATAL: sorry, too many clients already

Thank you for any suggestions.

Christoph

One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

5

On Wed, Apr 29, 2015 at 3:46 PM, Mike Grogan <d.michael.grogan@anonymised.com>
wrote:

Before you switch to JNDI, I would be interested to see how many postgres
connections you show with the psql command "select datid, datname, pid,
client_addr, client_port, state, query from pg_stat_activity;." Do your
number of connections increase each time you harvest a granule? Just
wondering if you are seeing the same thing as me. I should have opened a
JIRA issue on this, but the transition to the new JIRA was ongoing and then
I got lazy.

The new Jira is operational, if you want to give it a shot now :slight_smile:

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

6

Hello Mike, Andrea,

I started the query, you mentioned. I have currently 128 rows.
After ingesting an image via REST to a mosaic, I had 129 rows.

Will these connections get a timeout or something like that after some time?

Is that still the same behaviour you had? Is it worth to create an issue
in JIRA?

Thank you for the link with the instructions and the additional hints.

Kind regards,
Christoph

Am 29.04.2015 15:46, schrieb Mike Grogan:

Instructions can be found
at: http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_datastore.html.
See the JNDI section. One warning, I found that the
minEvictableIdleTimeMillis and timeBetweenEvictionRunsMillis
settings in the examples seemed to oddly cause me problems with stale
database connections that didn't seem to get validated before re-use.

Take a look at this user list conversation between Andrea and
me: http://osgeo-org.1560.x6.nabble.com/postgres-connection-exhaustion-Image-Mosaic-Harvesting-td5200863.html

It discusses the connection exhaustion issue I was seeing when
harvesting granules via REST and discusses transitioning to JNDI.

Before you switch to JNDI, I would be interested to see how many
postgres connections you show with the psql command "select datid,
datname, pid, client_addr, client_port, state, query from
pg_stat_activity;." Do your number of connections increase each time
you harvest a granule? Just wondering if you are seeing the same
thing as me. I should have opened a JIRA issue on this, but the
transition to the new JIRA was ongoing and then I got lazy.

Thanks,

Mike Grogan

On Wed, Apr 29, 2015 at 9:09 AM, Christoph Kleih <me@anonymised.com
<mailto:me@anonymised.com>> wrote:

    Dear Mike,

    thank you for your response.
    I am setting the database information in the datastore.properties
    file. Does it make sense to switch to JNDI?
    Can I still activate that?

    Thank you,
    Christoph

    Am 29.04.2015 15:04, schrieb Mike Grogan:

    Christoph,

    Are you using JNDI or just directly setting your database
    settings in the datastore.properties file? I ask this because I
    was seeing what looked like a connection starvation / connection
    leak issue harvesting image mosaic granules without using JNDI.
    Your "too many clients already" error makes me wonder if you are
    seeing a similar issue.

    - Mike

    On Tue, Apr 28, 2015 at 6:59 AM, Christoph Kleih <me@anonymised.com
    <mailto:me@anonymised.com>> wrote:

        Dear all,

        I am running geoserver 2.7.0 on a Ubuntu 14.04.

        I am using the REST interface to append images to a mosaic
        time series. That works fine. But some things happen in the
        logfiles which I cannot explain.

        May be you can give me an advice, what I can improve, to
        solve some of the below mentioned log messages.

        Here are the excerpts from the logfiles:

        postgres logfile:
        2015-04-28 12:28:56 CEST ERROR: stats for
        "my_layer.the_geom" do not exist
        2015-04-28 12:28:56 CEST CONTEXT: SQL function
        "st_estimated_extent" statement 2
        2015-04-28 12:28:56 CEST STATEMENT: select
        ST_AsText(ST_force_2d(ST_Envelope(ST_Estimated_Extent('public',
        'my_layer', 'the_geom'))))

        geoserver logfile:
        2015-04-28 10:29:48,857 WARN [geotools.jdbc] - Failed to use
        ST_Estimated_Extent, falling back on envelope aggregation
        org.postgresql.util.PSQLException: ERROR: stats for
        "my_layer.the_geom" do not exist
          Wobei: SQL function "st_estimated_extent" statement 2
            at
        org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)
           
         description=Features from JDBCDataStore
        2015-04-28 10:33:52,648 WARN [imagemosaic.catalog] - This
        granule catalog was not properly dispose as it still points
        to: ServiceInfo
         description=Features from JDBCDataStore

        Is that connected with this:
        http://docs.geoserver.org/stable/en/user/data/database/primarykey.html

        After many ingestions, I also get this message in the
        postgres log:
        2015-04-27 18:48:04 CEST FATAL: sorry, too many clients already

        Thank you for any suggestions.

        Christoph

        ------------------------------------------------------------------------------
        One dashboard for servers and applications across
        Physical-Virtual-Cloud
        Widest out-of-the-box monitoring support with 50+ applications
        Performance metrics, stats and reports that give you
        Actionable Insights
        Deep dive visibility with transaction tracing using APM Insight.
        http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
        _______________________________________________
        Geoserver-users mailing list
        Geoserver-users@lists.sourceforge.net
        <mailto:Geoserver-users@lists.sourceforge.net>
        https://lists.sourceforge.net/lists/listinfo/geoserver-users

7

Yes, that is what I was seeing … for every REST call to harvest, a new db connection was made. To know if you’re seeing the same, it would probably be better to do more than just 1 harvest … if you were to make maybe 10 or so REST calls and verify that the number of db connections also increased by 10, I think we could say you were seeing the same behavior.

  • Mike
···

On Wed, Apr 29, 2015 at 11:39 AM, Christoph Kleih <me@anonymised.com> wrote:

Hello Mike, Andrea,

I started the query, you mentioned. I have currently 128 rows.
After ingesting an image via REST to a mosaic, I had 129 rows.

Will these connections get a timeout or something like that after some time?

Is that still the same behaviour you had? Is it worth to create an issue in JIRA?

Thank you for the link with the instructions and the additional hints.

Kind regards,
Christoph

Am 29.04.2015 15:46, schrieb Mike Grogan:

Instructions can be found at: http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_datastore.html. See the JNDI section. One warning, I found that the minEvictableIdleTimeMillis and timeBetweenEvictionRunsMillis settings in the examples seemed to oddly cause me problems with stale database connections that didn’t seem to get validated before re-use.

Take a look at this user list conversation between Andrea and me: http://osgeo-org.1560.x6.nabble.com/postgres-connection-exhaustion-Image-Mosaic-Harvesting-td5200863.html

It discusses the connection exhaustion issue I was seeing when harvesting granules via REST and discusses transitioning to JNDI.

Before you switch to JNDI, I would be interested to see how many postgres connections you show with the psql command “select datid, datname, pid, client_addr, client_port, state, query from pg_stat_activity;.” Do your number of connections increase each time you harvest a granule? Just wondering if you are seeing the same thing as me. I should have opened a JIRA issue on this, but the transition to the new JIRA was ongoing and then I got lazy.

Thanks,

Mike Grogan

On Wed, Apr 29, 2015 at 9:09 AM, Christoph Kleih <me@anonymised.com> wrote:

Dear Mike,

thank you for your response.
I am setting the database information in the datastore.properties file. Does it make sense to switch to JNDI?
Can I still activate that?

Thank you,
Christoph

Am 29.04.2015 15:04, schrieb Mike Grogan:

Christoph,

Are you using JNDI or just directly setting your database settings in the datastore.properties file? I ask this because I was seeing what looked like a connection starvation / connection leak issue harvesting image mosaic granules without using JNDI. Your “too many clients already” error makes me wonder if you are seeing a similar issue.

  • Mike

On Tue, Apr 28, 2015 at 6:59 AM, Christoph Kleih <me@anonymised.com> wrote:

Dear all,

I am running geoserver 2.7.0 on a Ubuntu 14.04.

I am using the REST interface to append images to a mosaic time series. That works fine. But some things happen in the logfiles which I cannot explain.

May be you can give me an advice, what I can improve, to solve some of the below mentioned log messages.

Here are the excerpts from the logfiles:

postgres logfile:
2015-04-28 12:28:56 CEST ERROR: stats for “my_layer.the_geom” do not exist
2015-04-28 12:28:56 CEST CONTEXT: SQL function “st_estimated_extent” statement 2
2015-04-28 12:28:56 CEST STATEMENT: select ST_AsText(ST_force_2d(ST_Envelope(ST_Estimated_Extent(‘public’, ‘my_layer’, ‘the_geom’))))

geoserver logfile:
2015-04-28 10:29:48,857 WARN [geotools.jdbc] - Failed to use ST_Estimated_Extent, falling back on envelope aggregation
org.postgresql.util.PSQLException: ERROR: stats for “my_layer.the_geom” do not exist
Wobei: SQL function “st_estimated_extent” statement 2
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)

description=Features from JDBCDataStore
2015-04-28 10:33:52,648 WARN [imagemosaic.catalog] - This granule catalog was not properly dispose as it still points to: ServiceInfo
description=Features from JDBCDataStore

Is that connected with this:
http://docs.geoserver.org/stable/en/user/data/database/primarykey.html

After many ingestions, I also get this message in the postgres log:
2015-04-27 18:48:04 CEST FATAL: sorry, too many clients already

Thank you for any suggestions.

Christoph

One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

8

On Wed, Apr 29, 2015 at 3:04 PM, Mike Grogan <d.michael.grogan@anonymised.com>
wrote:

Christoph,

Are you using JNDI or just directly setting your database settings in the
datastore.properties file? I ask this because I was seeing what looked
like a connection starvation / connection leak issue harvesting image
mosaic granules without using JNDI. Your "too many clients already" error
makes me wonder if you are seeing a similar issue.

Found time to look into this one, after a long investigation confirmed we
are leaking connections and found where, still working on a solution:
https://osgeo-org.atlassian.net/browse/GEOS-7024

About the JNDI connections, I've also updated the tutorials to include what
we are using for production JNDI pools here:
http://docs.geoserver.org/latest/en/user/tutorials/tomcat-jndi/tomcat-jndi.html

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

9

Thanks, Andrea! For the JNDI-based pools, I’ll test soon with your example settings.

  • Mike
···

On Fri, May 15, 2015 at 10:32 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Wed, Apr 29, 2015 at 3:04 PM, Mike Grogan <d.michael.grogan@anonymised.com> wrote:

Christoph,

Are you using JNDI or just directly setting your database settings in the datastore.properties file? I ask this because I was seeing what looked like a connection starvation / connection leak issue harvesting image mosaic granules without using JNDI. Your “too many clients already” error makes me wonder if you are seeing a similar issue.

Found time to look into this one, after a long investigation confirmed we are leaking connections and found where, still working on a solution:
https://osgeo-org.atlassian.net/browse/GEOS-7024

About the JNDI connections, I’ve also updated the tutorials to include what we are using for production JNDI pools here:
http://docs.geoserver.org/latest/en/user/tutorials/tomcat-jndi/tomcat-jndi.html

Cheers

Andrea

–

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.