BF 7.1.2.1 Scheduled jobs kick off two builds instead of one
I have two systems (SystemA and SystemB) both running BF 7.1.2.1 build 90.
SystemA has 12 scheduled jobs and SystemB has 39 scheduled jobs. Right now, SystemA behaves normally. But SystemB kicks off two identical builds for each scheduled job. Does anyone know what might be the cause? Is there a work around? Thanks. |
3 answers
I have two systems (SystemA and SystemB) both running BF 7.1.2.1 build 90. if there are 2 instances of the engine running out of the same directory this can happen. The lock bfsched uses is based on the engine ID which is generated and kept in the engine working directory. check for a process "bfsched" to see how many are running. You may have to kill an extra "bfsched" and "buildforge" (add .exe if this is windows) |
We have 2 management consoles (7.1.2) both pointing to the same DB. The reason is (1) Users can get to BF via the URL for either server and (2) the load of running jobs can be "balanced" (I know it's not pure balancing) across two MCs.
What I am seeing is that some, but not all, scheduled jobs are executing on BOTH MCs. Anyone else observe this behavior? --Jeff |
We have 2 management consoles (7.1.2) both pointing to the same DB. The reason is (1) Users can get to BF via the URL for either server and (2) the load of running jobs can be "balanced" (I know it's not pure balancing) across two MCs. Hi, That sounds like 'PM39101 Clustered engines run scheduled jobs twice' that was fixed in the 7.1.3 release. The release notes are at https://jazz.net/downloads/rational-build-forge/releases/7.1.3?p=releasenotes . Brent |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.