Hi Uwe, Jukka,
Thanks for the testimonies and the anaysis.
I checked there are two timeout in the code
connectTimeout : was 5 s, is still 5 s
readTimeout : was 5 s, is now 10 s
Changed in r4448
Michaël
Le 11/06/2015 14:14, Uwe Dalluege a écrit :
> Hi Jukka,
>
> thank you very much for the inter
Revision: 4488
http://sourceforge.net/p/jump-pilot/code/4488
Author: michaudm
Date: 2015-06-11 19:59:57 + (Thu, 11 Jun 2015)
Log Message:
---
Set the WMS ReadTimeout from 5 to 10 s (connect timeout is unchanged)
Modified Paths:
--
core/trunk/src/com/vivi
Hi Jukka,
thank you very much for the interesting test.
Maybe it is a solution that the user can choose
in OJ the timeout.
But I don't know how complicated this is.
Greetings from a sunny Hamburg :-)
Uwe
Am 11.06.2015 um 14:03 schrieb Rahkonen Jukka (MML):
> Hi,
>
> I confirm that old OJ vers
Hi,
I confirm that old OJ versions seem to have a longer timeout and they can
contact that geoportal server reliably. The server is responding sometimes
within 5 seconds but more often it takes longer. Increasing timeout to 10
seconds feels good to me but I wonder if even that could be too stri
Hi Michaël,
I received a mail from a German OJ user (OJ 1.8.0-r4164-plus)
with the same problem like you have (timeout) with the url:
http://www.geoproxy.geoportal-th.de/geoproxy/services?VERSION=1.1.1&;
He told me that *it works* with OJ Version 1.6.3-r3576-plus.
Unfortunately I can no reprodu
