This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Java errors in Garmin Connect

Recently bought an Edge 200 Bike GPS. Finding the Connect software a bit clunky and continually experiencing Java errors in both Firefox and Internet Explorer. Most frustrating issue is Java errors part way through creating a new course which completely loses the route created up to the crash and requiring starting again from scratch. Tearing my hair out! Any ideas, can't see an existing thread for my problem but can't imagine I'm alone in experiencing it.
  • Former Member
    0 Former Member over 9 years ago
    Same issue

    I came out here to find an answer to the same problem....nobody has responded to this yet? Since June?

    Your Connect page loads correctly only 1.5 times out of 10 in Chrome 47.0. Consistently not loading Calendar or Activities data. Requires many re-loads to get data in these tiles. Link from Activities spawns a page full of socket timeout errors.
    Garmin, please respond in a timely manner.

    A little shaky walking down the aisle makes me wonder how the marriage is going to be.
  • Former Member
    0 Former Member over 9 years ago
    Recently bought an Edge 200 Bike GPS. Finding the Connect software a bit clunky and continually experiencing Java errors in both Firefox and Internet Explorer. Most frustrating issue is Java errors part way through creating a new course which completely loses the route created up to the crash and requiring starting again from scratch. Tearing my hair out! Any ideas, can't see an existing thread for my problem but can't imagine I'm alone in experiencing it.


    What you're seeing is server-side java, nothing to do with any java installation that you may or may not have on your machine. There's a lot of servelet/tomcat stuff in the errors. It's not for users to have any ideas, as it's not our problem to fix.

    I saw a lot of socket errors and the like, either back-end stuff is dying or having capacity issues, somewhere in the frontend->api->services stack (stereotypically). It's a job for the Connect server operations and dev people to fix. Please stop tearing your hair out- as it's not your fault :)

    (..and it has been rather bad today, whatever it is.)
  • It seems to work ok now!!

    I must admit to forgetting about this problem after not receiving any replies and have since found alternative methods for creating my routes. However, I have tried creating routes in Connect today and all have worked ok without any problem. Only difference on my pc between then and now is an update to Windows 10 and a few Java updates. I'll revert back to using Connect to create routes as it really is a lot easier than my alternative method when it works and hopefully all will be ok now. Thanks for reminding me of the problem, I forget so much these days!!