It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884
×6,033
×76

question asked: Nov 02 '15, 6:05 p.m.
question was seen: 3,509 times
last updated: Nov 03 '15, 10:36 a.m.

Related questions

What does this RTC JBE message mean?

0
Randall Beck (22●4●13) | asked Nov 02 '15, 6:05 p.m.
We are seeing this error in the RTC JBE log file
2015-11-02 16:27:01 [Jazz build engine] Waiting for request...
2015-11-02 16:31:35 [Jazz build engine] Found a user request for build definition "IPM Packaging 8.1.2 Extension".
Nov 2, 2015 4:36:38 PM com.ibm.team.filesystem.client.internal.LoggingHelper logSEVERE: Status ERROR: com.ibm.team.filesystem.client code=0 Job Broadcasting local changes has been in state 1 for too long null

Environment
  • Red Hat Enterprise Linux Server release 6.7
  • plenty of RAM and disk space
  • RTC 5.0.2, ifix6

Observations
  • a normal build is 2 minutes
  • after a restart of the JBE, several builds are successful
  • in a few hours though, a build request starts, but becomes "orphaned" i.e., the Eclipse client shows it is still running, but the Linux build engine does not show the build PID
  • The JBE then becomes unusable, i.e., no one is able to request a build; new build requests wait
  • We noticed that .jazz5/.jazzlock persists and has same timestamp as the orphaned build log
  • We've searched jazz.net and Google and found nothing helpful about this specific error message

Comments
Kevin Ramer commented Nov 03 '15, 10:36 a.m.

Found an entry in Ralph's Excellent Blog:

https://rsjazz.wordpress.com/2015/04/07/the-day-the-jbe-stood-still/

Looks like JBE needs 32 bit JDK which we will try shortly.

Be the first one to answer this question!

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.