Related
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

Is Garmin Connect down at the moment?

Former Member
Former Member over 9 years ago
Hi

When connecting to https://connect.garmin.com/modern/ using firefox, I get the following response (inside the blue border):

Internal Error

Sorry, we encountered an internal error.

Details
User doesn't have proper roles.
com.garmin.web.DashboardController.populateDefaultModel(DashboardController.java:626)
com.garmin.web.DashboardController.dashboard(DashboardController.java:142)
sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:606)
org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:219)
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132)
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:746)
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:687)
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80)
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:925)
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856)
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:915)
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:811)
javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:796)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
com.garmin.web.service.util.XHttpMethodOverrideFilter.doFilterInternal(XHttpMethodOverrideFilter.java:62)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
com.garmin.web.filter.sso.AuthenticationFilter.doFilter(AuthenticationFilter.java:161)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:44)
org.jasig.cas.client.util.AssertionThreadLocalFilter.doFilter(AssertionThreadLocalFilter.java:63)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
org.jasig.cas.client.util.HttpServletRequestWrapperFilter.doFilter(HttpServletRequestWrapperFilter.java:86)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
com.garmin.security.cas.client.validation.AbstractTicketValidationFilter.doFilter(AbstractTicketValidationFilter.java:389)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
com.garmin.security.cas.client.authentication.UnprotectedAuthenticationFilter.doFilter(UnprotectedAuthenticationFilter.java:98)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
com.garmin.security.cas.client.session.SingleSignOutFilter.doFilter(SingleSignOutFilter.java:92)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
com.garmin.security.cas.client.util.ExcludedURLDetectionFilter.doFilter(ExcludedURLDetectionFilter.java:68)
com.garmin.web.filter.sso.ConditionalFilterChain.doFilter(ConditionalFilterChain.java:41)
com.garmin.web.filter.sso.ConditionalFilter.doFilter(ConditionalFilter.java:81)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:197)
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:1805)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
java.lang.Thread.run(Thread.java:745)


Will this explain the sync issues I'm having (via mobile app and express)
Werner
  • 0 over 9 years ago
    It would have been nice to have known this was occurring, maybe a push notification on your connect app and maybe a splash screen online saying down for maintenance. But I do agree that a cloud based serve should never be down. And you should always be able to login and shnc with your phone etc even if the website is being maintenanced this way once it's back up your phone just syncs with the Web. This is very frustrating because it practically make the device on my wrist nothing more than a fancy watch.


    There was a message at the top of Garmin Connect (website) all week stating that there would be downtime for maintenance starting last night.
  • Former Member
    0 Former Member over 9 years ago
    Garmin in poor communication shock.....

    If Apple ever nail a sports watch Garmin will be in trouble.


    I am a Apple fan but the price points make that impossible. The VA just needs the HR added and then it will be unbeatable to the Apple watch and £100 lower.
  • Former Member
    0 Former Member over 9 years ago
    If your business is depending on cloud (and Garmin is moving in that direction), then you need parallel servers, so you can play with one while users are using other.


    you are presuming this is a cloud issue and I doubt that as the errors are java and this is part of the app upgrade etc.

    Their twitter feed not updated now for 8 hours and before that promises it would be back soon, that is just poor comms. OK they may be based on West coast of the States but still should be updating with someone over the night.
  • 0 over 9 years ago
    Pretty sure

    I'm pretty sure that there was someone on scene all night, probably consuming enough coffee to make the Folger's stock go up 3 points, and generating some unique, new language at the systems. Having been in IT for 20+ years, (now retired), I can only imagine what's going on in the server room(s) at Garmin.. Hectic would come no where near. Patience, my children, patience, remember, all good things come to those who wait!
  • Former Member
    0 Former Member over 9 years ago
    I'm pretty sure that there was someone on scene all night, probably consuming enough coffee to make the Folger's stock go up 3 points, and generating some unique, new language at the systems. Having been in IT for 20+ years, (now retired), I can only imagine what's going on in the server room(s) at Garmin.. Hectic would come no where near. Patience, my children, patience, remember, all good things come to those who wait!


    Well said... those in IT will know the feeling you get in the stomach whilst 'scheduled maintenance' is under way and EVERYONE is looking at you to do your job smoothly and on time. Especially when there's a companies reputation on the line. Good luck to those doing the maintenance work, hope everything is going smoothly :)
  • 0 over 9 years ago
    They did post a banner about 3 days prior at the top of the Garmin Connect site warning of maintenance downtime on the 11th. I don't recall if the banner gave a time estimation or not. Couldn't upload a workout I did at around 9PM, PST and am frankly a little surprised it is still down. I hope they get it up and running soon.
  • Former Member
    0 Former Member over 9 years ago
    you are presuming this is a cloud issue and I doubt that as the errors are java and this is part of the app upgrade etc.


    I am using term 'cloud' in sense that my data is somewhere 'there' on Internet and I am not able to use my device fully without connection to their servers. If you adopt that strategy and you are pushing customers in that direction then you are responsible to provide continuous service.

    I am not blaming IT guys for this, but management, because there are ways to avoid this, not by buying more coffee to sysadmins, but to buy/lease redundant servers. Imagine Amazon with downtime of 10 hours, they know it is not acceptable, Garmin (management) obviously think for them (and their customers) it is.
  • 0 over 9 years ago
    As long as it is not down for more than a day I am fine with that.
  • Former Member
    0 Former Member over 9 years ago
    Well comeing back now but sync still not working and website looks unfortunately the same
  • Former Member
    0 Former Member over 9 years ago
    Support is clueless to the issue

    I just spoke with a guy in their Kansas support center and he was totally unaware of any issues with Connect. He was actually suggesting that it might be my phone. Mind you, I have been using the app on my phone (prior to the upgrade) for about 3 weeks without issue. Since the update to 5.0 on my Fenix 3, syncing has been an issue and now connect doesn't work.

    They should do an internal audit of their policies of delivering code (perhaps a Beta) before distributing it to their entire customer base. They are creating opportunity for other companies.