Announcement

Collapse
No announcement yet.

Many read timeouts these days

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Many read timeouts these days

    Hello,
    After the usgs astrogeology page (which now seems Ok), I can observe read time outs on Nasa worldwind servers... Is there a problem ? Which is the current working number ? I'm talking about the first 3 layers (except the very first one, which is an image of course). I tried to extend connection time outs to 30s with no success.
    Any hints ?
    Thanks
    --frenchy

  • #2
    Good and bad news Frenchy, fortunately, mostly good!

    We're rolling out https certificates for a couple of the servers this week. I imagine the issue you are seeing is due to some reconfiguration efforts by our system administer. During the roll out period World Wind servers may be a little rocky while all of the bugs are ironed out.

    If you don't think that is the issue, let me know!
    Zach
    World Wind Team
    https://github.com/NASAWorldWind

    Comment


    • #3
      I have read timeouts on Political Borders now, making big yellow fronteers when zooming in.
      Is the server down ?
      Txs

      Comment


      • #4
        Same with online demos.
        Thanks to FAO borders alternatives.

        Comment


        • #5
          Sorry Frenchy, another case of good news bad news.

          All the https certs and endpoints are in place; however, the server caching isn't functioning yet in the new configuration. Please be patient as the servers reimplement some functionality.

          The online demos were updated today in coordination with the v2.1.0 release. We've been testing them most of the day with success, so if you're having issues, let us know!
          Zach
          World Wind Team
          https://github.com/NASAWorldWind

          Comment


          • #6
            Today, the Place Names layer worked from the east coast of the USA, but when I ran WW remotely in Europe, the Place Names layer didn't load. I figure a server is probably temporarily offline somewhere, but I thought I'd mention the issue just in case it is something else.

            Comment


            • #7
              Thanks for the heads up, turns out the server was having some issues. It should be working now.
              Zach
              World Wind Team
              https://github.com/NASAWorldWind

              Comment


              • #8
                Maybe your server/s are still having a few problems. My app is having problems downloading Bing and most other layers. I have a setup that can print each of the request strings in a .bat file.

                http://worldwind27.arc.nasa.gov/wms/...st=GetMap&vers
                ion=1.1.1&srs=EPSG:4326&layers=ve&styles =&transparent=TRUE&format=image/png&widt
                h=512&height=512&bbox=-119.232421875,34.13671875,-119.21484375,34.154296875
                #552
                http://worldwind27.arc.nasa.gov/wms/...st=GetMap&vers
                ion=1.1.1&srs=EPSG:4326&layers=ve&styles =&transparent=TRUE&format=image/png&widt
                h=512&height=512&bbox=-119.21484375,34.154296875,-119.2060546875,34.1630859375
                #552
                http://worldwind27.arc.nasa.gov/wms/...st=GetMap&vers
                ion=1.1.1&srs=EPSG:4326&layers=ve&styles =&transparent=TRUE&format=image/png&widt
                h=512&height=512&bbox=-119.2412109375,34.171875,-119.232421875,34.1806640625
                #552

                copy/paste the string in an address bar will download the single requested image but the app which I have not had a problem like this AFAIR. will not display or ad that image to the cache,
                note: this uses the older http rather than https. Can my affected layer files be updated to solve this or will I need to update to the latest wwj build or wait for your server glitches to be resolved?

                Any chance of a C++ port of NWW in 2017 ??
                Happy New Year
                Neil
                Neil
                http://www.nlneilson.com

                Comment


                • #9
                  As of late last month, the NASA World Wind Servers (worldwind*.arc.nasa.gov and data.arc.nasa.gov and builds.arc.nasa.gov) only implement https connections. When an http connection is attempted, a permanent (301) redirect to the https connection is returned. Browsers automatically follow the redirect but the Java client does not, which is likely the reason it works when you attempt to paste the request in the address bar of a browser. Before the end of last month, the http connection was still available and thus there was no redirect returned.

                  The solution is changing the connection type to https, which, can be as simple as an update to your layer configurations, or updating to v2.1.0 which includes a number of fixes as well as updated layer configurations.

                  Your existing cached layer data/imagery should be unaffected by the switch to the https configuration. The new data/imagery delivered via https with be cached appropriately in the existing structure alongside http data.

                  Zach
                  World Wind Team
                  https://github.com/NASAWorldWind

                  Comment


                  • #10
                    Thanks for the explanation including the timeline. I will try just updating the layers. It has been several year since updating to a later build, I downloaded v2.1.0 but it may be awhile before doing a complete update. The online demo worked OK for the Bing/ Virtual Earth images.

                    Neil
                    Neil
                    http://www.nlneilson.com

                    Comment


                    • #11
                      Neil,

                      The team noticed some of the external data sources disappeared. We've marked them as deprecated in v2.1.0. They'll still work with your existing on disk cache, but the servers don't seem to be responding anymore so no new imagery will be available. This is all stuff you probably know, but I wanted to give you a heads up and encourage you to check out the complete config directory in the v2.1.0 release.

                      This release should be completely compatible with v2.0.0, but let us know if you have any issues if/when you migrate.

                      Zach
                      Zach
                      World Wind Team
                      https://github.com/NASAWorldWind

                      Comment


                      • #12
                        I-cubed Landsat is crashing now ? I have numerous read-time-outs, while just surfing above Earth at 10,000m...

                        Comment


                        • #13
                          Frenchy, everything seems okay today. Have you noticed any more problems with the I-cubed Landsat imagery?
                          Zach
                          World Wind Team
                          https://github.com/NASAWorldWind

                          Comment


                          • #14
                            Hi Zach,
                            Much less since one day or two, but I just had one now at 22H37 Paris/Berlin Time, maybe you can check that in your servers logs.
                            Txs

                            java.net.SocketTimeoutException: Read timed out
                            at java.net.SocketInputStream.socketRead0(N ative Method)
                            at java.net.SocketInputStream.socketRead(Un known Source)
                            at java.net.SocketInputStream.read(Unknown Source)
                            at java.net.SocketInputStream.read(Unknown Source)
                            at sun.security.ssl.InputRecord.readFully(U nknown Source)
                            at sun.security.ssl.InputRecord.read(Unknow n Source)
                            at sun.security.ssl.SSLSocketImpl.readRecor d(Unknown Source)
                            at sun.security.ssl.SSLSocketImpl.performIn itialHandshake(Unknown Source)
                            at sun.security.ssl.SSLSocketImpl.startHand shake(Unknown Source)
                            at sun.security.ssl.SSLSocketImpl.startHand shake(Unknown Source)
                            at sun.net.http://www.protocol.https.HttpsClien...onnect(Unknown Source)
                            at sun.net.http://www.protocol.https.AbstractDe...onnect(Unknown Source)
                            at sun.net.http://www.protocol.http.HttpURLConn...tream0(Unknown Source)
                            at sun.net.http://www.protocol.http.HttpURLConn...Stream(Unknown Source)
                            at java.net.HttpURLConnection.getResponseCo de(Unknown Source)
                            at sun.net.http://www.protocol.https.HttpsURLCo...seCode(Unknown Source)
                            at gov.nasa.worldwind.retrieve.HTTPRetrieve r.doRead(HTTPRetriever.java:46)
                            at gov.nasa.worldwind.retrieve.URLRetriever .read(URLRetriever.java:329)
                            at gov.nasa.worldwind.retrieve.URLRetriever .call(URLRetriever.java:234)
                            at gov.nasa.worldwind.retrieve.URLRetriever .call(URLRetriever.java:1)
                            at java.util.concurrent.FutureTask.run(Unkn own Source)
                            at gov.nasa.worldwind.retrieve.RetrievalTas k.run(RetrievalTask.java:40)
                            at java.util.concurrent.ThreadPoolExecutor. runWorker(Unknown Source)
                            at java.util.concurrent.ThreadPoolExecutor$ Worker.run(Unknown Source)
                            at java.lang.Thread.run(Unknown Source)
                            Last edited by frenchy; 09-20-2017, 11:01 AM. Reason: added client stack

                            Comment


                            • #15
                              Sorry guys, it is not the Landsat imagery which is failing but the place names server still (worldwind22), so it is a known issue.
                              I just commented out the test on the exception type in the URLRetriever.read() method, making all errors logged anyway.
                              Code:
                              protected ByteBuffer read() throws Exception {
                                      try {
                                          ByteBuffer buffer = this.doRead(this.connection);
                                          if (buffer == null)
                                              this.contentLength = 0;
                                          return buffer;
                                      } catch (Exception e) {
                                          // if (!(e instanceof SocketTimeoutException || e instanceof UnknownHostException || e instanceof SocketException)) {
                                          Logging.logger().log(Level.SEVERE, Logging.getMessage("URLRetriever.ErrorReadingFromConnection", this.url.toString()), e);
                                          // }
                                          throw e;
                                      }
                                  }
                              Example of URL failing at some time (cumulated data? no data ?)
                              https://worldwind22.arc.nasa.gov/geo...25,-50.0,-20.0
                              Txs to eventually look at that.
                              -frenchy
                              Last edited by frenchy; 09-28-2017, 10:54 AM.

                              Comment

                              Working...
                              X