SCM leaves a job running; is this a bug or a usage error?
![]()
Jonathan Wildstrom (1●1●1)
| asked Sep 27 '12, 10:51 a.m.
retagged Dec 16 '13, 4:07 p.m. by David Lafreniere (4.8k●7)
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
![]()
Shashikant Padur (4.2k●2●7)
| answered Oct 01 '12, 12:37 a.m.
JAZZ DEVELOPER edited Oct 01 '12, 12:37 a.m.
It is similar to workitem 49609. Does this message show up on every command run on the console?
Comments I don't actually know. I wasn't doing detailed work from the command line, just getting properties. It sometimes shows up, and sometimes doesn't. Okay, we will track this in the workitem mentioned above. |
![]()
what is the work around for this problem ....????
|
![]()
Following it up in the defect.
|