What does this error message mean: CRJAZ1992E The task "com.ibm.team.repository.com.ibm.team.scm.monitorScrub" has failed with an unexpected error...The error message is "CRJAZ1411E Database connection has been closed. Check database status & ....?
We are receiving the following error message in the RTC diagnostics:
CRJAZ1992E The task "com.ibm.team.repository.com.ibm.team.scm.monitorScrub" has failed with an unexpected error which has caused it to be unscheduled. The error message is "CRJAZ1411E Database connection has been closed. Check database status and availability.". Please check your server logs for details. Once you have addressed the issues, you should restart the server to reschedule this background task.
I have checked the server logs and the database availability. I can find no complaints in the logs themselves and everything seems to be working as expected.
We are running RTC 3.0.1.1 and an Oracle 11.2.0.1.4 database.
What does this reported error mean and how do we correct it?
|
6 answers
CRJAZ1992E The task "com.ibm.team.process.RequestRemoteEnterpriseProcessUpdatesTask" has failed with an unexpected error which has caused it to be unscheduled. The error message is "Failed to prepare connection". Please check your server logs for details. Once you have addressed the issues, you should restart the server to reschedule this background task. Resolved the above error by increasing the JDBC Connection Pool Wait time from its defualt value of 3000 to 6000. Ran the diagnostics and no errors reported. Comments
Simon Eickel
commented Jul 11 '13, 12:52 a.m.
Hi Madhu,
Jaygee Santos
commented Jul 20 '13, 10:55 a.m.
We also received this error on our JTS server currently on v4.0.0. Increasing the JDBC connection pool wait time fixed the problem! What is the impact though when this task fails? I am curious because we have recently been getting intermittent timeout errors from users when loading workspaces. |
I am getting the same error ID but with "
Comments 1
Tiia Laitinen
commented Jan 21 '13, 4:55 a.m.
We getting this same error too, version is also 4.0.1.
Michael Prentice
commented Jan 24 '13, 10:56 a.m.
We are seeing this with 4.0.1 as well. We just increased the heap size in DB2 and changed from circular to archival logging to support hot backups.
Would either of those changes cause this error? How do we fix it?
Gordon Flood
commented Mar 08 '13, 2:07 p.m.
We are seeing this same top level error code with 4.0.1 (build RJF-I20121109-1457). We have just upgraded from 3.x and switched from data mart to data warehouse. The top level error text, like Mike, is
The nested error that caused it to fail, like Mike, is database related, but different:
Can we get some information on this in 4.01?? Here's our full nested error:
|
You're likely encountering the issue described under the section Problem 1 of defect 182246. This was fixed in 3.0.1.3 so you should probably look to upgrade in order to solve this issue.
|
Hello, we still have the same problem in RTC version 3.0.1.3, but with Oracle
|
We have the same problem.
RTC 3.0.1.3 , Oracle 11.2 |
We are observing the same problem on v4.0.1.
CRJAZ1992E The task "com.ibm.team.process.RequestRemoteEnterpriseProcessUpdatesTask" has failed with an unexpected error which has caused it to be unscheduled. The error message is "Failed to prepare connection". Please check your server logs for details. Once you have addressed the issues, you should restart the server to reschedule this background task.
Isn't there any other solution to resolve this issue apart from restarting the server?
Best Regards
Comments
Madhu Prabhu
commented May 02 '13, 9:21 a.m.
See the exact same error: CRJAZ1992E The task "com.ibm.team.process.RequestRemoteEnterpriseProcessUpdatesTask" has failed with an unexpected error which has caused it to be unscheduled. The error message is "Failed to prepare connection". Please check your server logs for details. Once you have addressed the issues, you should restart the server to reschedule this background task. Please update if you found a resolution for this issue.... |
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.