[BAM-20730] Master or branch plan Bitbucket Server triggered stop working

Type: Bug
Resolution: Fixed
Priority: Low
Fix Version/s: 6.10.4
Affects Version/s: 6.8.1
Component/s: Triggers
Labels:
None

Symptom Severity:
Severity 3 - Minor
Bug Fix Policy:
View Atlassian Server bug fix policy

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

Enable debug logging:

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

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

mentioned in: Page Failed to load

Patricio made changes - 30/Apr/2020 9:05 AM

Description

Original: h3. Issue Summary
Bitbucket Server trigger stop working for a particular master or branch plan randomly. Restarting Bamboo will make it works again

h3. Steps to Diagnose
# Enable debug logging:
{noformat}
com.atlassian.bamboo.plugins.stash.events.BranchChangedEventListener
com.atlassian.bamboo.plan.NonBlockingPlanExecutionServiceImpl
{noformat}
# 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:
{noformat}
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

{noformat}

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

New: h3. Issue Summary

Bitbucket Server trigger stops working for a particular master or branch plan randomly. Restarting Bamboo will make it work again.
h3. Steps to Diagnose
# Enable debug logging:
{noformat}
com.atlassian.bamboo.plugins.stash.events.BranchChangedEventListener
com.atlassian.bamboo.plan.NonBlockingPlanExecutionServiceImpl
{noformat}

# 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:
{noformat}
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

{noformat}

h3. Workaround

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

ferrari made changes - 14/Feb/2020 7:46 PM

Remote Link

New: This issue links to "Page (Confluence)" [ 471165 ]

Foong (Inactive) made changes - 27/Nov/2019 6:05 AM

Description

Original: h3. Issue Summary
Bitbucket Server trigger stop working for a particular master or branch plan randomly. Restarting Bamboo will make it works again

h3. Steps to Diagnose
Randomly happen
# Enable debug logging:
{noformat}
com.atlassian.bamboo.plugins.stash.events.BranchChangedEventListener
com.atlassian.bamboo.plan.NonBlockingPlanExecutionServiceImpl
{noformat}
# 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:
{noformat}
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

{noformat}

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

New: h3. Issue Summary
Bitbucket Server trigger stop working for a particular master or branch plan randomly. Restarting Bamboo will make it works again

h3. Steps to Diagnose
# Enable debug logging:
{noformat}
com.atlassian.bamboo.plugins.stash.events.BranchChangedEventListener
com.atlassian.bamboo.plan.NonBlockingPlanExecutionServiceImpl
{noformat}
# 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:
{noformat}
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

{noformat}

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

Alexey Chystoprudov made changes - 26/Nov/2019 11:47 AM

Resolution		New: Fixed [ 1 ]
Status	Original: In Progress [ 3 ]	New: Closed [ 6 ]

Alexey Chystoprudov made changes - 26/Nov/2019 11:47 AM

Status

Original: Needs Triage [ 10030 ]

New: In Progress [ 3 ]

Foong (Inactive) made changes - 26/Nov/2019 10:26 AM

Description

Original: h3. Issue Summary
Bitbucket Server trigger stop working for a particular master or branch plan randomly. Restarting Bamboo will make it works again

h3. Steps to Diagnose
Randomly happen
# Enable debug logging:
{noformat}
com.atlassian.bamboo.plugins.stash.events.BranchChangedEventListener
com.atlassian.bamboo.plan.NonBlockingPlanExecutionServiceImpl
{noformat}
# atlassian-bamboo.log file shows that Bamboo receive Bitbucket Server trigger but did not start queue polling job:
{noformat}
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

{noformat}

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

New: h3. Issue Summary
Bitbucket Server trigger stop working for a particular master or branch plan randomly. Restarting Bamboo will make it works again

h3. Steps to Diagnose
Randomly happen
# Enable debug logging:
{noformat}
com.atlassian.bamboo.plugins.stash.events.BranchChangedEventListener
com.atlassian.bamboo.plan.NonBlockingPlanExecutionServiceImpl
{noformat}
# 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:
{noformat}
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

{noformat}

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

Foong (Inactive) made changes - 26/Nov/2019 10:25 AM

Assignee

New: Alexey Chystoprudov [ achystoprudov ]

Foong (Inactive) made changes - 26/Nov/2019 10:25 AM

Fix Version/s

New: 6.10.4 [ 89690 ]

Foong (Inactive) made changes - 26/Nov/2019 10:24 AM

Description

Original: h3. Issue Summary
Bitbucket Server trigger stop working for a particular master or branch plan randomly. Restarting Bamboo will make it works again

h3. Steps to Reproduce
Randomly happen
# Enable debug logging:
{noformat}
com.atlassian.bamboo.plugins.stash.events.BranchChangedEventListener
com.atlassian.bamboo.plan.NonBlockingPlanExecutionServiceImpl
{noformat}
# atlassian-bamboo.log file shows that Bamboo receive Bitbucket Server trigger but did not start queue polling job:
{noformat}
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

{noformat}

h3. Expected Results
sd

h3. Actual Results
sd

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

New: h3. Issue Summary
Bitbucket Server trigger stop working for a particular master or branch plan randomly. Restarting Bamboo will make it works again

h3. Steps to Diagnose
Randomly happen
# Enable debug logging:
{noformat}
com.atlassian.bamboo.plugins.stash.events.BranchChangedEventListener
com.atlassian.bamboo.plan.NonBlockingPlanExecutionServiceImpl
{noformat}
# atlassian-bamboo.log file shows that Bamboo receive Bitbucket Server trigger but did not start queue polling job:
{noformat}
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

{noformat}

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

Foong (Inactive) created issue - 26/Nov/2019 10:24 AM

Assignee:: Alexey Chystoprudov

Reporter:: Foong (Inactive)

Affected customers:: 0 This affects my team

Watchers:: 6 Start watching this issue

Created:: 26/Nov/2019 10:24 AM

Updated:: 28/Sep/2020 2:25 PM

Resolved:: 26/Nov/2019 11:47 AM

Details

Description

Issue Summary

Steps to Diagnose

Workaround

Attachments

Issue Links

Forms

Activity

People

Dates