Issue Summary

Bitbucket Server trigger stops working for a particular master or branch plan randomly. Restarting Bamboo will make it work again.

Steps to Diagnose

1. Enable debug logging:

   com.atlassian.bamboo.plugins.stash.events.BranchChangedEventListener
   com.atlassian.bamboo.plan.NonBlockingPlanExecutionServiceImpl
   

1. atlassian-bamboo.log file shows that Bamboo receive Bitbucket Server trigger but did not start queue polling job even though the previous build have finished and it does not receive any other trigger:

   2019-10-18 11:56:37,720 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-6] [BranchChangedEventListener] Received Bitbucket Server ref changed event PROJ/reponame::branchname
   2019-10-18 11:56:37,722 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-6] [BranchChangedEventListener] publishing change detection event for PROJ-PLAN2
   2019-10-18 11:56:37,722 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-6] [BranchChangedEventListener] publishing change detection event for PROJ-PLAN2
   2019-10-18 11:56:37,723 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-9] [NonBlockingPlanExecutionServiceImpl] Did not start queue polling job, CHAIN:PROJ-PLAN2 is already being executed
   2019-10-18 11:56:37,723 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-4] [NonBlockingPlanExecutionServiceImpl] Did not start queue polling job, CHAIN:PROJ-PLAN2 is already being executed
   
   

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available