If agent fails to fetch AdministrationConfiguration, the error is cached indefinitely

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • 9.4.2, 9.2.8, 9.3.6
    • Affects Version/s: 9.2.7
    • Component/s: Agents
    • None
    • 1
    • Severity 2 - Major

      Issue Summary

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. It's very random, with no actual reproduction outside of hand-crafted scenarios involving deliberately breaking the agent - server communication.

      Expected Results

      After a communication error agent retries the operations

      Actual Results

      If agent -server communication timeouts, subsequent calls simply rethrow the exception

      The below exception is thrown in the atlassian-bamboo.log file:

      org.springframework.remoting.RemoteTimeoutException: Receive timeout after 300000 ms for RemoteInvocation: method name 'getAdministrationConfiguration'; parameter types []
INFO   | jvm 1364 | 2023/11/20 11:02:26 |   at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2086) ~[guava-32.1.2-jre.jar:?]
INFO   | jvm 1364 | 2023/11/20 11:02:26 |   at com.google.common.cache.LocalCache.get(LocalCache.java:4012) ~[guava-32.1.2-jre.jar:?]
INFO   | jvm 1364 | 2023/11/20 11:02:26 |   at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:4035) ~[guava-32.1.2-jre.jar:?]
(...)
Caused by: org.springframework.remoting.RemoteTimeoutException: Receive timeout after 300000 ms for RemoteInvocation: method name 'getAdministrationConfiguration'; parameter types []
INFO   | jvm 1364 | 2023/11/20 11:02:26 |   at org.springframework.jms.remoting.JmsInvokerClientInterceptor.onReceiveTimeout(JmsInvokerClientInterceptor.java:393) ~[spring-jms-5.3.29.jar:5.3.29]
INFO   | jvm 1364 | 2023/11/20 11:02:26 |   at org.springframework.jms.remoting.JmsInvokerClientInterceptor.executeRequest(JmsInvokerClientInterceptor.java:261) ~[spring-jms-5.3.29.jar:5.3.29]
INFO   | jvm 1364 | 2023/11/20 11:02:26 |   at org.springframework.jms.remoting.JmsInvokerClientInterceptor.invoke(JmsInvokerClientInterceptor.java:206) ~[spring-jms-5.3.29.jar:5.3.29]
INFO   | jvm 1364 | 2023/11/20 11:02:26 |   at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(Reflect

      Workaround

      There are two possible workarounds:

      Workaround 1

      • Restart affected agents.

      Workaround 2

      • Trigger a change in administration configuration and then revert it. This causes event broadcast to all agents and should clear the cached value (or in this case: error).

            Assignee:
            Marcin Gardias
            Reporter:
            Marcin Gardias
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: