SCM leaves a job running; is this a bug or a usage error?
I'm running a large number of property gets back-to-back (getting properties of all files in my workspace to check file metadata as part of a project clone). I regularly seem to get the following error:
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: com.ibm.team.filesystem.rcp.core.internal.changes.util.listeners.UpdateChangesJob
The command I'm running is:
for dir in <directory list>; do find $dir -type f | xargs scm property list; done
Am I doing something wrong, or is there a bug in the SCM tools that leaves something running?
I'm running RTC 4.0.0.1; this also happened ion RTC 4.0.
6 answers
I have the same problem as well with Jenkins and the Team Center plugin by Rational and RTC version 4.0.1 -- How do I resolve this? What do I do to "shutdown" things?
Comments
From defect 49609...
Do you have a .snap file under <workspace>/.metadata/.plugins/org.eclipse.core.resources/ ? If so, delete it and rerun the command. This would be a workaround until we fix the issue.
I ended up deleting the whole workspace (from the directory containing .jazz5 on down).
Hi,
I am seeing this problem frequently in my build environment. We have a Jenkins plugin called "Maven Release Plugin" that we use to automate our maven release process, however it needs to deliver changes back in to RTC and I would say we hit this error about 25% of the time. It has become a real burden to our team to keep having to cleanup the failed release each time. We are on RTC 4.0.6, and the problem still seems to be there, so wondering if we know what version of RTC this was addressed in. We are looking to upgrade to RTC some time Next year.
Thanks!
I am seeing this problem frequently in my build environment. We have a Jenkins plugin called "Maven Release Plugin" that we use to automate our maven release process, however it needs to deliver changes back in to RTC and I would say we hit this error about 25% of the time. It has become a real burden to our team to keep having to cleanup the failed release each time. We are on RTC 4.0.6, and the problem still seems to be there, so wondering if we know what version of RTC this was addressed in. We are looking to upgrade to RTC some time Next year.
Thanks!
