Navigation

    TripleA Logo

    TripleA Forum

    • Register
    • Login
    • Search
    • TripleA Website
    • Categories
    • Recent
    • Popular
    • Users
    • Groups
    • Tags

    [Open] Connection Lost

    (ARCHIVED) Bug Reports
    6
    29
    7203
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • V
      VanBattlesick last edited by

      I tried option one. I will try the other one next.

      1 Reply Last reply Reply Quote 0
      • ssoloff
        ssoloff Admin last edited by

        @RoiEX I'm cleaning up my fork. Do you still need the spike/topic-1104-connection-lost-debugging branch? If you don't need it now but think you'll need it again in the future, it's pretty simple to re-create.

        1 Reply Last reply Reply Quote 0
        • RoiEX
          RoiEX Admin last edited by

          Not anymore. We have all the debug information we can get for now, so we should be fine

          1 Reply Last reply Reply Quote 1
          • ssoloff
            ssoloff Admin @RoiEX last edited by

            @RoiEX said in Connection Lost:

            I finally found the post where I proposed the original solution.
            I modified the properties file to be

            handlers=games.strategy.debug.ConsoleHandler
            
            games.strategy.net.nio.NioWriter.level=FINEST
            games.strategy.net.nio.NioReader.level=FINEST
            

            but unfortunately I got a

            Can't load log handler "games.strategy.debug.ConsoleHandler"
            java.lang.InstantiationException: games.strategy.debug.ConsoleHandler
            

            Because the ConsoleHandler class no longer has a default constructor.
            So we need a code change either way unfortunately, adding a default constructor might be the fastest way nevertheless though.

            I was playing around with the logging system recently. I discovered that specifying the games.strategy.debug.ConsoleHandler in the configuration file appears to be unnecessary since it is registered in code during application startup. That means you can remove the handlers property to avoid the InstantiationException, but the logger level configuration lines continue to be processed as expected.

            In summary, even though our ConsoleHandler doesn't provide a default constructor, the approach you proposed above should continue to be a viable solution if we ever need to provide a custom logger configuration (at least with respect to log levels).

            1 Reply Last reply Reply Quote 2
            • V
              VanBattlesick last edited by

              Hi,
              Sorry I have not updated on what happened while playing but I got so fed up that I just said "Forget it!". I find myself still wanting to play at times however and now wonder if their has been any progress with a fix for my problem. What else can I do to make this work?
              VanB.........

              1 Reply Last reply Reply Quote 0
              • RoiEX
                RoiEX Admin last edited by

                @VanBattlesick You wanted to try option 2

                1 Reply Last reply Reply Quote 0
                • J
                  James Fisher @VanBattlesick last edited by

                  This post is deleted!
                  1 Reply Last reply Reply Quote 0
                  • L
                    liqik last edited by liqik

                    I tried it again with a different map and it still showed the same.

                    I only realised recently that https://speedtestfast.com/verizon-speed-test/ is a speed test site that shows you accurate data on the streaming speeds you can get on Netflix, as it uses the same CDN servers used by Netflix video streams.

                    1 Reply Last reply Reply Quote 0
                    • RoiEX
                      RoiEX Admin last edited by

                      Unfortunately there's not really a lot we can do about it 😕

                      However if that helps, @LaFayette is currently putting a lot of effort into rewriting parts of the networking code, so maybe that'll fix this problem as a nice side-effect in the future.
                      No guarantees though.

                      1 Reply Last reply Reply Quote 0
                      • 1
                      • 2
                      • 2 / 2
                      • First post
                        Last post
                      Copyright © 2016-2018 TripleA-Devs | Powered by NodeBB Forums