CRJAZ1992E The task "com.ibm.team.enterprise.buildablesubset.BuildableSubsetMigrationTask" has failed with an unexpected error which has caused it to be unscheduled. The error message is "Dependency query failed". Please check your server logs for details
3 answers
Hi Zica,
Although the following forum post does not specifically reference the background task noted in this question, I believe it is relevant
https://jazz.net/forum/questions/118828/error-message-background-task-crjaz1992e
Although the following forum post does not specifically reference the background task noted in this question, I believe it is relevant
https://jazz.net/forum/questions/118828/error-message-background-task-crjaz1992e
Hi Zica,
After increasing the timeout, does it take longer for the problem to occur. If yes, then there may be some resource contention. I would suggest looking into the jvm, thread pool settings. Also at the time the problem is logged, review the jts/ccm/db/server logs to see if there were any unusual behavior.
If after going through the log analysis/ tuning exercise and the issue continues, I would suggest openning a PMr with support to continue the investigation.
After increasing the timeout, does it take longer for the problem to occur. If yes, then there may be some resource contention. I would suggest looking into the jvm, thread pool settings. Also at the time the problem is logged, review the jts/ccm/db/server logs to see if there were any unusual behavior.
If after going through the log analysis/ tuning exercise and the issue continues, I would suggest openning a PMr with support to continue the investigation.
Hi Zica,
The BuildableSubsetMigrationTask is started on server startup and does migration of buildable subset. The buildable subset is artifact related to Enterprise Extensions - Dependency Build function. When you perform diagnostic, the server is not ready for any migration tasks to run. Unfortunately, the BuildableSubsetMigrationTask does not check for the server status before trying to perform the migration. However, it shouldn't impact the server at all. It's just an error seeing on the admin or server log. We have a work item to handle this issue Execute startup migration logic only when set up has been performed (274050).
Comments
Krzysztof Kaźmierczyk
Jul 25 '13, 4:19 a.m.Hello Zica,
Could you look into your ccm.log file to see what is entire stack trace there?