It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787
×10,826
×1,192

question asked: Jul 01 '14, 2:26 p.m.
question was seen: 5,165 times
last updated: Jul 09 '14, 6:29 p.m.

Related questions

FAQ - How this Forum works

Help Using BuildForge with RTC 4.0.6

0
Andrés Hurtado (6●1●2) | asked Jul 01 '14, 2:26 p.m.
edited Jul 01 '14, 2:27 p.m.
Hello

We have already deployed RTC 4.0.6 (on RHEL 6.3 and DB2 20.1) and need to enable automatic build and deploy for some projects. For this purpose we have decided to use BuildForge (7.1.3.4), since the organization where we're working already had it.

On overall .... we couldn't make it work.

Ahead I'm giving more context on what we did, in case anyone could give us any advice.

- Both (RTC and BF) authenticate users with LDAP. However on BuildForge we had to create a user within the application, because for some reason we couldn´t use the BF LDAP user with the RTC build engine (with the non-ldap user, worked perfectly)

- We configured the integration using this article (https://jazz.net/library/article/607). It's for an older version of RTC, but it was the most comprehensive guide we could find.

- The steps followed were:

1.- We configured the testing project JUnit, and started the execution on BuildForge. First step seems successfully executed, but the second failed because it couldn't find the source code to build using the ant script.

2.- We checked the file JazzJBE.xml to understand why the source code isn't extracted from RTC, but couldn't identify which part of this file commands the source code extraction.

3.- When we tried to run the project again, BuildForge couldn’t find the adapter.

4.- Was applied a reset over the template adapter (ass suggested on one topic in the jazz forum).

5.- We tried to run again the project, however the buildforge job got stuck on starting state, without any change. Investigating we discovered that buildforge engine stopped.

6.- Since then each time we launch the job, trying to create a build from RTC, the buildforge engine stops and we must start it all over again.

Our main concern is to understand why the buildforge engine stops.

Then we need to understand why (for the only time it worked) we couldn’t get the source code.

And finally, we are worried about the problem related to the BuildForge LDAP user, which cannot be used within the RTC build engine. This user was used within BuildForge without problem, so shouldn’t be a permissions problem,

Thanks in advance! 

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Spencer Murata (2.3k●11●59●71) | answered Jul 01 '14, 2:59 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Using a LDAP user for the engine is not recommended.  That user will be locked out of the Build Forge console while the RTC integration is in use.  And if the password expires, the user will likely be locked out immediately, causing an outage.  It is safer to go with a local BF user.  However if you absolutely must, remember to use the domain of the user in bf like so DOMAIN\user when setting up the LDAP user in RTC.

As far as the engine stopping, what does the catalina.log show for Build Forge?
0
permanent link
Andrés Hurtado (6●1●2) | answered Jul 02 '14, 5:37 p.m.
 Hi!

On the BF user, we agree with you. Thanks for letting us confirm what we thought.
Below is what catalina.out shows. However always appears the same, doesn’t matter if the project was executed or not.
I’ve looked into another logs, but none of them hints where the error is occurring.

Thanks again for your help.

 Jun 30, 2014 11:54:27 PM com.buildforge.services.server.manager.fti.AuditLogManagerImpl submit
SEVERE: submit: LOST AUDIT LOG: AuditLogDBO[uuid=null,auditClass=Build,type=Update,userUuid=1,targetUuid=df6dff870c691000ee5fcb345c0c5c0c,stamp=1404186863,text=BUILD_12,details={sxJobTag=BUILD_12, sxJobUuid=df6dff870c691000ee5fcb345c0c5c0c, sxProjectName=rtc_build_junit_with_JBE, sxProjectUuid=de2bc3d70c691000acd8cb3459d959d9}]
Throwable occurred: com.buildforge.services.common.api.APIException: CRRBF2670E: Unable to initialize Full Text Index for class [com.buildforge.services.server.manager.fti.AuditLogManagerImpl].
        at com.buildforge.services.server.manager.fti.meta.AbstractFtiManagerImpl.ftiError(AbstractFtiManagerImpl.java:121)
        at com.buildforge.services.server.manager.fti.meta.AbstractFtiManagerImpl.getFtiWriter(AbstractFtiManagerImpl.java:882)
        at com.buildforge.services.server.manager.fti.AuditLogManagerImpl.getFtiWriterCached(AuditLogManagerImpl.java:197)
        at com.buildforge.services.server.manager.fti.AuditLogManagerImpl.submit(AuditLogManagerImpl.java:309)
        at com.buildforge.services.server.manager.fti.AuditLogManagerImpl.submit(AuditLogManagerImpl.java:261)
        at com.buildforge.services.server.manager.fti.AuditLogManagerImpl.submit(AuditLogManagerImpl.java:209)
        at com.buildforge.services.server.manager.fti.meta.Auditor.auditUpdate(Auditor.java:203)
        at com.buildforge.services.server.manager.BuildManager.update(BuildManager.java:645)
        at com.buildforge.services.server.manager.BuildManager.completeBuild(BuildManager.java:2047)
        at com.buildforge.services.server.api.commands.BuildCommands.completeBuild(BuildCommands.java:411)
        at com.buildforge.services.server.api.commands.BuildCommands.invoke(BuildCommands.java:170)
        at com.buildforge.services.server.api.APICommandProcessor.process(APICommandProcessor.java:290)
        at com.buildforge.services.server.api.APIServerConnection.handleRequest(APIServerConnection.java:257)
        at com.buildforge.services.server.api.APIServerConnection.process(APIServerConnection.java:171)
        at com.buildforge.services.server.dispatch.callback.BufferedConnection.run(BufferedConnection.java:246)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
        at java.lang.Thread.run(Thread.java:736)
Caused by: java.io.IOException: read past EOF
        at java.lang.Throwable.<init>(Throwable.java:67)
        at org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java:201)
        at org.apache.lucene.store.BufferedIndexInput.readByte(BufferedIndexInput.java:39)
        at org.apache.lucene.store.ChecksumIndexInput.readByte(ChecksumIndexInput.java:40)
        at org.apache.lucene.store.IndexInput.readInt(IndexInput.java:71)
        at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:260)
        at org.apache.lucene.index.IndexFileDeleter.<init>(IndexFileDeleter.java:168)
        at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1155)
        at com.buildforge.services.server.manager.fti.meta.AbstractFtiManagerImpl.getFtiWriter(AbstractFtiManagerImpl.java:878)
        ... 16 more
Jun 30, 2014 11:58:50 PM com.buildforge.services.server.manager.BuildEnvironmentManager deleteBulk
INFO: Removed 6 orphan build environments in 133ms.
Comments
Spencer Murata commented Jul 07 '14, 9:05 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

You should open a PMR on that error.  Something is likely not configured correctly, there shouldn't be an EOF problem completing the build, but that could mean many different possible causes.


~Spencer

Andrés Hurtado commented Jul 09 '14, 6:29 p.m.

Thanks a lot!

We will try it! 

Your answer

Register or to post 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.