It's all about the answers!

Ask a question

The build engine process may not be running - Build Forge - RTC Integration


sergio cortes (122) | asked Oct 23 '13, 1:20 a.m.
 Hello
 
Our build definitions in Rational Team Concert are randomly showing the following warning message "The build engine process may not be running" and every attempt to request a build from the RTC Eclipse or RTC Web interface results in pending state until the request are manually cancelled.
 
The Build-Forge server and all his agents are running and we can request a build from the build-forge web interface without any problem also we can test the connection from the Build-Engine screen and its OK. 
 
This problems persist until we restart the RTC Server and the RTC Database. Sometimes we can work with the RTC - Build Forge integration for weeks until this problem appears and we need to restart the servers.
 
Do you know the origin for the warning message "The build engine process may not be running" when using BuildForge Engines with Rational Team Concert? And the best way to solve this problem 
 
Currently we are using Rational Team Concert 4.0.1 and Build-Forge 7.1.3.4
 
Thanks in advance.

One answer



permanent link
Nick Edgar (6.5k611) | answered Oct 23 '13, 11:47 a.m.
JAZZ DEVELOPER
Hi Sergio, the Build Forge integration consists of two background tasks:
1) looks up pending builds in RTC and creates a corresponding build in BF
2) monitors events from BF for build started/completed and step started/completed, and updates the RTC build accordingly

Are the builds in pending state or in progress?  If pending, that indicates the 1st task isn't running properly (and the 2nd is thus irrelevant).  If in progress, then it sounds like the 1st task is running OK but the 2nd isn't running properly.  I'll assume the former since you actually said "pending" and "cancelled".

Can you check Active Services in the RTC admin web UI?  Does it show the BuildForgeBuildLoopScheduledTask (1st one) and/or BuildForgeEventPollerScheduledTask (2nd one) running?  If so, they may be held up on some other Build Forge engine with a bad connection configuration.

To get a full dump of the build engines in the repository, access the following URL as an admin user (otherwise you won't be able to see engines in projects not visible to you):
https://HOST:PORT/ccm/resource/virtual/builds/engines?_prettyPrint=true

You can then search for "buildforge" to see which of the engines are Build Forge flavoured, and what their configured domain and port are.


Comments
Alex Akilov commented Nov 05 '13, 9:54 a.m.

I get the following with the suggested URL:
  "errorClass": "java.lang.UnsupportedOperationException",

    "errorCode": 501,
    "errorMessage": "CRJAZ0916I There is no CRUD service registered for the location \"https:\/\/<ourserverURL>\/ccm\/service\/com.ibm.team.repository.common.internal.IVirtualRestService\/virtual\/builds\/engines\".",
    "errorTrace": [
        "com.ibm.team.repository.service.internal.crud.CrudUtils.getCrudService(CrudUtils.java:83)",


Nick Edgar commented Nov 05 '13, 10:53 a.m.
JAZZ DEVELOPER

Sorry, my mistake, it should be .../resource/virtual/build/engines?_prettyPrint=true 

(not builds).

Your answer


Register or to post your answer.