Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-20712

Bamboo queue fail to work properly due to duplicates

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 6.10.0
    • 6.5.0, 6.7.1, 6.9.2
    • Build Queues
    • None

      Issue Summary

      Bamboo queue fail to work properly due to duplicates

      Steps to Reproduce

      Steps may vary depending on each instance

      Expected Results

      No duplicates entries in the queue, since keys should always be unique

      Actual Results

      The following error is displayed in the server logs:

      2019-07-30 00:39:30,388 ERROR [PluginSchedulerTask-KubernetesIsolatedDockerImpl] [KubernetesWatchdog] Exception caught and swallowed to preserve rescheduling of the task
      java.lang.IllegalArgumentException: Multiple entries with same key: QueuedResultKey{resultKey=BP-FLL-CUIE-323, timestamp=16838536244288330}=com.atlassian.bamboo.v2.build.queue.BuildQueueManager$QueueItemView@78f5394d and QueuedResultKey{resultKey=BP-FLL-CUIE-323, timestamp=16838536244288330}=com.atlassian.bamboo.v2.build.queue.BuildQueueManager$QueueItemView@64ee5a78
          at com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:150)
          at com.google.common.collect.RegularImmutableMap.checkNoConflictInBucket(RegularImmutableMap.java:104)
          at com.google.common.collect.RegularImmutableMap.<init>(RegularImmutableMap.java:70)
          at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:254)
          at com.google.common.collect.Maps.uniqueIndex(Maps.java:1166)
          at com.google.common.collect.Maps.uniqueIndex(Maps.java:1140)
          at com.atlassian.bamboo.v2.build.queue.QueueManagerView.getQueueView(QueueManagerView.java:55)
          at com.atlassian.buildeng.spi.isolated.docker.DockerAgentBuildQueue.currentlyQueued(DockerAgentBuildQueue.java:72)
          at com.atlassian.buildeng.kubernetes.KubernetesWatchdog.executeImpl(KubernetesWatchdog.java:262)
          at com.atlassian.buildeng.kubernetes.KubernetesWatchdog.execute(KubernetesWatchdog.java:107)
          at com.atlassian.sal.core.scheduling.TimerPluginScheduler$PluginTimerTask.run(TimerPluginScheduler.java:75)
          at java.util.TimerThread.mainLoop(Timer.java:555)
          at java.util.TimerThread.run(Timer.java:505)
      

      Workaround

      Upgrade to a version of Bamboo higher or equal to 6.10.0.

            [BAM-20712] Bamboo queue fail to work properly due to duplicates

            Andrei made changes -
            Description Original: h3. Issue Summary

            Bamboo queue fail to work properly due to duplicates

            h3. Steps to Reproduce
            Steps may vary depending on each instance

            h3. Expected Results
            No duplicates entries in the queue, since keys should always be unique

            h3. Actual Results
            The following error is displayed in the server logs:
            {noformat}
            2019-07-30 00:39:30,388 ERROR [PluginSchedulerTask-KubernetesIsolatedDockerImpl] [KubernetesWatchdog] Exception caught and swallowed to preserve rescheduling of the task
            java.lang.IllegalArgumentException: Multiple entries with same key: QueuedResultKey{resultKey=BP-FLL-CUIE-323, timestamp=16838536244288330}=com.atlassian.bamboo.v2.build.queue.BuildQueueManager$QueueItemView@78f5394d and QueuedResultKey{resultKey=BP-FLL-CUIE-323, timestamp=16838536244288330}=com.atlassian.bamboo.v2.build.queue.BuildQueueManager$QueueItemView@64ee5a78
                at com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:150)
                at com.google.common.collect.RegularImmutableMap.checkNoConflictInBucket(RegularImmutableMap.java:104)
                at com.google.common.collect.RegularImmutableMap.<init>(RegularImmutableMap.java:70)
                at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:254)
                at com.google.common.collect.Maps.uniqueIndex(Maps.java:1166)
                at com.google.common.collect.Maps.uniqueIndex(Maps.java:1140)
                at com.atlassian.bamboo.v2.build.queue.QueueManagerView.getQueueView(QueueManagerView.java:55)
                at com.atlassian.buildeng.spi.isolated.docker.DockerAgentBuildQueue.currentlyQueued(DockerAgentBuildQueue.java:72)
                at com.atlassian.buildeng.kubernetes.KubernetesWatchdog.executeImpl(KubernetesWatchdog.java:262)
                at com.atlassian.buildeng.kubernetes.KubernetesWatchdog.execute(KubernetesWatchdog.java:107)
                at com.atlassian.sal.core.scheduling.TimerPluginScheduler$PluginTimerTask.run(TimerPluginScheduler.java:75)
                at java.util.TimerThread.mainLoop(Timer.java:555)
                at java.util.TimerThread.run(Timer.java:505)
            {noformat}

            h3. Workaround
            Upgrade to a version of Bamboo higher than 6.10.0.
            New: h3. Issue Summary

            Bamboo queue fail to work properly due to duplicates

            h3. Steps to Reproduce
            Steps may vary depending on each instance

            h3. Expected Results
            No duplicates entries in the queue, since keys should always be unique

            h3. Actual Results
            The following error is displayed in the server logs:
            {noformat}
            2019-07-30 00:39:30,388 ERROR [PluginSchedulerTask-KubernetesIsolatedDockerImpl] [KubernetesWatchdog] Exception caught and swallowed to preserve rescheduling of the task
            java.lang.IllegalArgumentException: Multiple entries with same key: QueuedResultKey{resultKey=BP-FLL-CUIE-323, timestamp=16838536244288330}=com.atlassian.bamboo.v2.build.queue.BuildQueueManager$QueueItemView@78f5394d and QueuedResultKey{resultKey=BP-FLL-CUIE-323, timestamp=16838536244288330}=com.atlassian.bamboo.v2.build.queue.BuildQueueManager$QueueItemView@64ee5a78
                at com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:150)
                at com.google.common.collect.RegularImmutableMap.checkNoConflictInBucket(RegularImmutableMap.java:104)
                at com.google.common.collect.RegularImmutableMap.<init>(RegularImmutableMap.java:70)
                at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:254)
                at com.google.common.collect.Maps.uniqueIndex(Maps.java:1166)
                at com.google.common.collect.Maps.uniqueIndex(Maps.java:1140)
                at com.atlassian.bamboo.v2.build.queue.QueueManagerView.getQueueView(QueueManagerView.java:55)
                at com.atlassian.buildeng.spi.isolated.docker.DockerAgentBuildQueue.currentlyQueued(DockerAgentBuildQueue.java:72)
                at com.atlassian.buildeng.kubernetes.KubernetesWatchdog.executeImpl(KubernetesWatchdog.java:262)
                at com.atlassian.buildeng.kubernetes.KubernetesWatchdog.execute(KubernetesWatchdog.java:107)
                at com.atlassian.sal.core.scheduling.TimerPluginScheduler$PluginTimerTask.run(TimerPluginScheduler.java:75)
                at java.util.TimerThread.mainLoop(Timer.java:555)
                at java.util.TimerThread.run(Timer.java:505)
            {noformat}

            h3. Workaround
            Upgrade to a version of Bamboo higher or equal to 6.10.0.
            Andrei made changes -
            Description Original: h3. Issue Summary

            Bamboo queue fail to work properly due to duplicates

            h3. Steps to Reproduce
            Steps may vary depending on each instance

            h3. Expected Results
            No duplicates entries in the queue, since keys should always be unique

            h3. Actual Results
            The following error is displayed in the server logs:
            {noformat}
            2019-07-30 00:39:30,388 ERROR [PluginSchedulerTask-KubernetesIsolatedDockerImpl] [KubernetesWatchdog] Exception caught and swallowed to preserve rescheduling of the task
            java.lang.IllegalArgumentException: Multiple entries with same key: QueuedResultKey{resultKey=BP-FLL-CUIE-323, timestamp=16838536244288330}=com.atlassian.bamboo.v2.build.queue.BuildQueueManager$QueueItemView@78f5394d and QueuedResultKey{resultKey=BP-FLL-CUIE-323, timestamp=16838536244288330}=com.atlassian.bamboo.v2.build.queue.BuildQueueManager$QueueItemView@64ee5a78
                at com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:150)
                at com.google.common.collect.RegularImmutableMap.checkNoConflictInBucket(RegularImmutableMap.java:104)
                at com.google.common.collect.RegularImmutableMap.<init>(RegularImmutableMap.java:70)
                at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:254)
                at com.google.common.collect.Maps.uniqueIndex(Maps.java:1166)
                at com.google.common.collect.Maps.uniqueIndex(Maps.java:1140)
                at com.atlassian.bamboo.v2.build.queue.QueueManagerView.getQueueView(QueueManagerView.java:55)
                at com.atlassian.buildeng.spi.isolated.docker.DockerAgentBuildQueue.currentlyQueued(DockerAgentBuildQueue.java:72)
                at com.atlassian.buildeng.kubernetes.KubernetesWatchdog.executeImpl(KubernetesWatchdog.java:262)
                at com.atlassian.buildeng.kubernetes.KubernetesWatchdog.execute(KubernetesWatchdog.java:107)
                at com.atlassian.sal.core.scheduling.TimerPluginScheduler$PluginTimerTask.run(TimerPluginScheduler.java:75)
                at java.util.TimerThread.mainLoop(Timer.java:555)
                at java.util.TimerThread.run(Timer.java:505)
            {noformat}

            h3. Workaround
            Upgrade to the latest version of Bamboo
            New: h3. Issue Summary

            Bamboo queue fail to work properly due to duplicates

            h3. Steps to Reproduce
            Steps may vary depending on each instance

            h3. Expected Results
            No duplicates entries in the queue, since keys should always be unique

            h3. Actual Results
            The following error is displayed in the server logs:
            {noformat}
            2019-07-30 00:39:30,388 ERROR [PluginSchedulerTask-KubernetesIsolatedDockerImpl] [KubernetesWatchdog] Exception caught and swallowed to preserve rescheduling of the task
            java.lang.IllegalArgumentException: Multiple entries with same key: QueuedResultKey{resultKey=BP-FLL-CUIE-323, timestamp=16838536244288330}=com.atlassian.bamboo.v2.build.queue.BuildQueueManager$QueueItemView@78f5394d and QueuedResultKey{resultKey=BP-FLL-CUIE-323, timestamp=16838536244288330}=com.atlassian.bamboo.v2.build.queue.BuildQueueManager$QueueItemView@64ee5a78
                at com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:150)
                at com.google.common.collect.RegularImmutableMap.checkNoConflictInBucket(RegularImmutableMap.java:104)
                at com.google.common.collect.RegularImmutableMap.<init>(RegularImmutableMap.java:70)
                at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:254)
                at com.google.common.collect.Maps.uniqueIndex(Maps.java:1166)
                at com.google.common.collect.Maps.uniqueIndex(Maps.java:1140)
                at com.atlassian.bamboo.v2.build.queue.QueueManagerView.getQueueView(QueueManagerView.java:55)
                at com.atlassian.buildeng.spi.isolated.docker.DockerAgentBuildQueue.currentlyQueued(DockerAgentBuildQueue.java:72)
                at com.atlassian.buildeng.kubernetes.KubernetesWatchdog.executeImpl(KubernetesWatchdog.java:262)
                at com.atlassian.buildeng.kubernetes.KubernetesWatchdog.execute(KubernetesWatchdog.java:107)
                at com.atlassian.sal.core.scheduling.TimerPluginScheduler$PluginTimerTask.run(TimerPluginScheduler.java:75)
                at java.util.TimerThread.mainLoop(Timer.java:555)
                at java.util.TimerThread.run(Timer.java:505)
            {noformat}

            h3. Workaround
            Upgrade to a version of Bamboo higher than 6.10.0.
            Patricio made changes -
            Fix Version/s New: 6.10.0 [ 86205 ]
            Patricio made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]

            Patricio added a comment -

            Fixed in version 6.10.0

            Patricio added a comment - Fixed in version 6.10.0
            Patricio created issue -

              Unassigned Unassigned
              pdemitrio Patricio
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: