Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

What causes "CRJAZ1990E"

From last 2 days, I have been receiving the below error:

One or more diagnostics is reporting a problem.  See details below.

The diagnostic "Background Task" reports an ERROR:

CRJAZ1990E 3 tasks have been unscheduled due to unexpected errors, including the task "com.ibm.team.repository.DbHeartbeat".  Please check your server logs for details.  Once you have addressed the issues, you should restart the server to reschedule this background task.

The JTS.log says: 2015-05-28 00:00:47,188 [                    Thread-407]  WARN org.apache.http.impl.client.DefaultHttpClient       - Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm="https%3A%2F%2Fclm.c-iv.org%2Fjts", oauth_problem="invalid_consumer_key"}

There is nothing in CCM.log for the same time.

I have restarted the server and will monitor if the issue comes back.

But want to understand, what is causing this issue? and how to fix it. Besides JTS and CCM, what are the relevant logs to check?

Please let me know.

0 votes

Comments

The DbHeartbeat can happen when the connectivity to the database is lost for more than a few minutes.   I have several RTC application servers that show this due to our SAN switches loosing power, thus causing our databases to fail until power was restored. 

RTC kept going for the most part, but the messages about scheduled tasks remains.

I would also add the suggestion to check any diagnostics on your database management system.

I got to know from the  DBA team that the number of minimum session connecting to database is 14 and maximum is 15. The sessions keep fluctuating between 14 and 15 and that is causing the disconnectivity of RTC application to Database.

Is there a way in setup of RTC/WAS/IHS/Jazz, that I can update the minimum and maximum number of sessions to be 15?

what is the recommended session value?

The database connection limit should be maintained by the database, not the application such as RTC. For general performance tuning, you can read the below article.
https://jazz.net/library/article/1029


Accepted answer

Permanent link
There is CLM limitation that once error appear for DbHeartbeat task, it does not dissapear even if the original issue is fixed. Therefore you must restart your server to the error disappear.

Regarding your error message, I would recommend you to look into ccm.log and see during the connection with which server this error appears.
Ralph Schoon selected this answer as the correct answer

0 votes

Comments

 I am getting this error for RM. Any advice? 

Read the comments and answers in this question or contact support.

1 vote

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,033

Question asked: May 28 '15, 12:40 p.m.

Question was seen: 4,122 times

Last updated: Sep 16 '20, 3:15 a.m.

Confirmation Cancel Confirm