[Geoserver-users] Geoserver ignoring socketTimeout setting in MapFish

GeoServer GeoServer User
1

Hi,

I have set my

**socketTimeout**

setting very high in my config.yaml file (Mapfish).

Tiles that return within 30 seconds from geoserver to mapfish works 100%. Problem comes in with very large raster tiles (that takes more than 30 seconds). In this case mapfish reports a Timed out error and the PDF is empty. It seems that geoserver ignores the socketTimeout setting in the Mapfish config.yaml file.

I am using the latest Geoserver (2.15.2) and Mapfish extension (geoserver-2.15.2-printing-plugin.zip).

Regards

Schalk

···

–

2

I think this file is only read by mapfish (not by geoserver).

Have you set connectionTimeout too? I think socketTimeout defaults to 180 seconds (180000), but connectionTimeout defaults to 30 seconds (which you mention below), so maybe that is the limiting condition here.

Brad

From: Schalk Grobbelaar schalk@anonymised.com
Sent: Monday, 8 July 2019 12:04 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] Geoserver ignoring socketTimeout setting in MapFish

Hi,

I have set my

**socketTimeout**

setting very high in my config.yaml file (Mapfish).

Tiles that return within 30 seconds from geoserver to mapfish works 100%. Problem comes in with very large raster tiles (that takes more than 30 seconds). In this case mapfish reports a Timed out error and the PDF is empty. It seems that geoserver ignores the socketTimeout setting in the Mapfish config.yaml file.

I am using the latest Geoserver (2.15.2) and Mapfish extension (geoserver-2.15.2-printing-plugin.zip).

Regards

Schalk

–

3

Hi Brad,

I have already tried setting both socketTimeout and connectionTimeout. Believe me, it is not that, but defnitely sockectTimeout ignored, because, like I said tiles that returns before 30 secods is getting treated by mapfish, otherwise it give timed out error. Since 2016 there was this problem. See:

https://sourceforge.net/p/geoserver/mailman/message/35025291/

···

On 08 Jul 2019 06:09, Brad Hards wrote:

I think this file is only read by mapfish (not by geoserver).

Have you set connectionTimeout too? I think socketTimeout defaults to 180 seconds (180000), but connectionTimeout defaults to 30 seconds (which you mention below), so maybe that is the limiting condition here.

Brad

From: Schalk Grobbelaar schalk@anonymised.com
Sent: Monday, 8 July 2019 12:04 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] Geoserver ignoring socketTimeout setting in MapFish

Hi,

I have set my

**socketTimeout**

setting very high in my config.yaml file (Mapfish).

Tiles that return within 30 seconds from geoserver to mapfish works 100%. Problem comes in with very large raster tiles (that takes more than 30 seconds). In this case mapfish reports a Timed out error and the PDF is empty. It seems that geoserver ignores the socketTimeout setting in the Mapfish config.yaml file.

I am using the latest Geoserver (2.15.2) and Mapfish extension (geoserver-2.15.2-printing-plugin.zip).

Regards

Schalk

–

4

Hi,

I have set my

**socketTimeout**

setting very high in my config.yaml file (Mapfish).

Tiles that return within 30 seconds from geoserver to mapfish works 100%. Problem comes in with very large raster tiles (that takes more than 30 seconds). In this case mapfish reports a Timed out error and the PDF is empty. It seems that geoserver ignores the socketTimeout setting in the Mapfish config.yaml file.

I am using the latest Geoserver (2.15.2) and Mapfish extension (geoserver-2.15.2-printing-plugin.zip).

Regards

Schalk

···

On 08 Jul 2019 06:09, Brad Hards wrote:

Hi,

I have set my

**socketTimeout**

setting very high in my config.yaml file (Mapfish).

Tiles that return within 30 seconds from geoserver to mapfish works 100%. Problem comes in with very large raster tiles (that takes more than 30 seconds). In this case mapfish reports a Timed out error and the PDF is empty. It seems that geoserver ignores the socketTimeout setting in the Mapfish config.yaml file.

I am using the latest Geoserver (2.15.2) and Mapfish extension (geoserver-2.15.2-printing-plugin.zip).

Regards

Schalk

5

Hi Schalk,
I had a look at the mapfish code, and unfortunately it looks that the version included in GeoServer print plugin (print-lib 2.1.4) ignores the timeouts in config.yaml.
They are now set in spring application context files.
You can find the one used by the geoserver plugin in the gs-printing jar (the file named applicationContext.xml). This means that those settings are currently hard-coded unless you extract and change that file in the jar.

Look for this section:

Mauro

···

Regards,

Mauro Bartolomeoli

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

Dott. Mauro Bartolomeoli
@mauro_bart
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy

mobile: +39 393 904 1756
phone: +39 0584 962313
fax: +39 0584 1660272

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.

6

Hi Mauro,

Wow,

Thanks for the fast feedback. I am not that familiar with extracting jar, modifying results and then putting it back into the jar. I only have basic Linux knowledge. Is it possible you can guide me in the right direction?

Best Regards

Schalk

···

On 09 Jul 2019 13:34, Mauro Bartolomeoli wrote:

Hi Schalk,
I had a look at the mapfish code, and unfortunately it looks that the version included in GeoServer print plugin (print-lib 2.1.4) ignores the timeouts in config.yaml.
They are now set in spring application context files.
You can find the one used by the geoserver plugin in the gs-printing jar (the file named applicationContext.xml). This means that those settings are currently hard-coded unless you extract and change that file in the jar.

Look for this section:

Mauro

Il giorno mar 9 lug 2019 alle ore 12:23 Schalk Grobbelaar <schalk@anonymised.com> ha scritto:

Hi,

I have set my

**socketTimeout**

setting very high in my config.yaml file (Mapfish).

Tiles that return within 30 seconds from geoserver to mapfish works 100%. Problem comes in with very large raster tiles (that takes more than 30 seconds). In this case mapfish reports a Timed out error and the PDF is empty. It seems that geoserver ignores the socketTimeout setting in the Mapfish config.yaml file.

I am using the latest Geoserver (2.15.2) and Mapfish extension (geoserver-2.15.2-printing-plugin.zip).

Regards

Schalk

On 08 Jul 2019 06:09, Brad Hards wrote:

Hi,

I have set my

**socketTimeout**

setting very high in my config.yaml file (Mapfish).

Tiles that return within 30 seconds from geoserver to mapfish works 100%. Problem comes in with very large raster tiles (that takes more than 30 seconds). In this case mapfish reports a Timed out error and the PDF is empty. It seems that geoserver ignores the socketTimeout setting in the Mapfish config.yaml file.

I am using the latest Geoserver (2.15.2) and Mapfish extension (geoserver-2.15.2-printing-plugin.zip).

Regards

Schalk

Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

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,

Mauro Bartolomeoli

== GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy

mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 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.

7

A jar is really just a zip file with a different extension. So you can edit files by just opening them with your
favouite zip tool, change the contents of the file, and the restart GeoServer to have the changes take effect

Cheers
Andrea

···

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.

8

Thanks Andrea,

Much appreciated.

···

Regards
Schalk

On 09 Jul 2019 14:00, Andrea Aime wrote:

A jar is really just a zip file with a different extension. So you can edit files by just opening them with your
favouite zip tool, change the contents of the file, and the restart GeoServer to have the changes take effect

Cheers
Andrea

On Tue, Jul 9, 2019 at 1:47 PM Schalk Grobbelaar <schalk@anonymised.com> wrote:

Hi Mauro,

Wow,

Thanks for the fast feedback. I am not that familiar with extracting jar, modifying results and then putting it back into the jar. I only have basic Linux knowledge. Is it possible you can guide me in the right direction?

Best Regards

Schalk

On 09 Jul 2019 13:34, Mauro Bartolomeoli wrote:

Hi Schalk,
I had a look at the mapfish code, and unfortunately it looks that the version included in GeoServer print plugin (print-lib 2.1.4) ignores the timeouts in config.yaml.
They are now set in spring application context files.
You can find the one used by the geoserver plugin in the gs-printing jar (the file named applicationContext.xml). This means that those settings are currently hard-coded unless you extract and change that file in the jar.

Look for this section:

Mauro

Il giorno mar 9 lug 2019 alle ore 12:23 Schalk Grobbelaar <schalk@anonymised.com> ha scritto:

Hi,

I have set my

**socketTimeout**

setting very high in my config.yaml file (Mapfish).

Tiles that return within 30 seconds from geoserver to mapfish works 100%. Problem comes in with very large raster tiles (that takes more than 30 seconds). In this case mapfish reports a Timed out error and the PDF is empty. It seems that geoserver ignores the socketTimeout setting in the Mapfish config.yaml file.

I am using the latest Geoserver (2.15.2) and Mapfish extension (geoserver-2.15.2-printing-plugin.zip).

Regards

Schalk

On 08 Jul 2019 06:09, Brad Hards wrote:

Hi,

I have set my

**socketTimeout**

setting very high in my config.yaml file (Mapfish).

Tiles that return within 30 seconds from geoserver to mapfish works 100%. Problem comes in with very large raster tiles (that takes more than 30 seconds). In this case mapfish reports a Timed out error and the PDF is empty. It seems that geoserver ignores the socketTimeout setting in the Mapfish config.yaml file.

I am using the latest Geoserver (2.15.2) and Mapfish extension (geoserver-2.15.2-printing-plugin.zip).

Regards

Schalk

Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

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,

Mauro Bartolomeoli

== GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy

mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 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:

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.