Hi Michaël, the German user said that it works with r4448. Thanks and greetings from him (and me too)!
Have a nice weekend. Uwe Am 11.06.2015 um 22:02 schrieb Michaël Michaud: > 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 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 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 strict? >>> Servers with loads of layers may be slow with generating GetCapabilities >>> because there can be lot of work to be done for computing the layer extents >>> etc. See the report below about failed trial with geoportal-th.de: >>> >>> SESSION STATE: Aborted. >>> The request was forwarded to the gateway. >>> Response Entity Size: 2231551 bytes. >>> >>> == FLAGS ================== >>> BitFlags: [ServerPipeReused, SentToGateway] 0x810 >>> X-ABORTED-WHEN: SendingResponse >>> X-CLIENTIP: 127.0.0.1 >>> X-CLIENTPORT: 64877 >>> X-EGRESSPORT: 64872 >>> X-PROCESSINFO: javaw:7200 >>> X-RESPONSEBODYTRANSFERLENGTH: 2231551 >>> X-SERVERSOCKET: REUSE ServerPipe#25 >>> >>> == TIMING INFO ============ >>> ClientConnected: 14:51:18.419 >>> ClientBeginRequest: 14:51:18.424 >>> GotRequestHeaders: 14:51:18.424 >>> ClientDoneRequest: 14:51:18.424 >>> Determine Gateway: 0ms >>> DNS Lookup: 0ms >>> TCP/IP Connect: 0ms >>> HTTPS Handshake: 0ms >>> ServerConnected: 14:50:49.009 >>> FiddlerBeginRequest: 14:51:18.427 >>> ServerGotRequest: 14:51:18.428 >>> ServerBeginResponse: 14:51:23.921 >>> GotResponseHeaders: 14:51:23.921 >>> ServerDoneResponse: 14:51:27.143 >>> ClientBeginResponse: 14:51:27.144 >>> ClientDoneResponse: 14:51:27.144 >>> >>> Overall Elapsed: 0:00:08.720 >>> >>> >>> -Jukka Rahkonen- >>> >>> Uwe Dalluege wrote: >>> >>> 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 reproduce this error. >>> Maybe you can reproduce it? >>> >>> Regards >>> >>> Uwe >>> >>> >>> Am 10.06.2015 um 13:51 schrieb Michaël Michaud: >>>> Hi, >>>> >>>> I get a socket timeout for a valid wms address. >>>> There are several places where a timeout is hardcoded in the WMS source : >>>> I have a url which does not use proxy and which timeout during the >>>> getCapability operation. >>>> Should I change the default timeout from 5000 to 10000 in the >>>> WMSService class ? >>>> >>>> Michaël >>>> >>>> >>>> ---------------------------------------------------------------------- >>>> -------- _______________________________________________ >>>> Jump-pilot-devel mailing list >>>> Jump-pilot-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> Jump-pilot-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > ------------------------------------------------------------------------------ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------------ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
