JBE 2.0.0.2iFix1 and ItemNotFound at load
Our RTC server is using 2.0.0 and I have reactivated our JBE service. First line of business is updating the JBE instance and the site offers the version in the subject.
The JBE is able to accept changes into the workspace but once the load into local workspace begins then it fails. The log contains the following line:
The same repository workspace downloads without errors in the RTC thick client. Is there a way to work around this? And is there also a way to find out what is being referred to byItem _mAmlYPNdEd2FwJTraqTVkA ? Thanks!
ciao!
The JBE is able to accept changes into the workspace but once the load into local workspace begins then it fails. The log contains the following line:
com.ibm.team.repository.common.ItemNotFoundException: Item _mAmlYPNdEd2FwJTraqTVkA is absent from configuration
at com.ibm.team.scm.client.internal.ConnectionBasedClientConfigurationProxy.fetch(ConnectionBasedClientConfigurationProxy.java:390)
at com.ibm.team.scm.client.internal.ConnectionBasedClientConfigurationProxy.fetchCompleteItem(ConnectionBasedClientConfigurationProxy.java:580)
at com.ibm.team.filesystem.client.internal.load.LoadRule.addLoadRules(LoadRule.java:98)
at com.ibm.team.build.internal.scm.ComponentLoadRules.getLoadRules(ComponentLoadRules.java:134)
at com.ibm.team.build.internal.scm.ComponentLoadRules.getLoadRules(ComponentLoadRules.java:177)
at com.ibm.team.build.internal.engine.JazzScmPreBuildParticipant.preBuild(JazzScmPreBuildParticipant.java:190)
at com.ibm.team.build.internal.engine.BuildLoop.invokePreBuildParticipants(BuildLoop.java:628)
at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:466)
at java.lang.Thread.run(Thread.java:735)
The same repository workspace downloads without errors in the RTC thick client. Is there a way to work around this? And is there also a way to find out what is being referred to by
ciao!
4 answers
Sorry for the delay in responding. It looks like the build definition specifies a load rule that can't be found. Can you check the 'Component load rules' field on the Jazz Source Control page of the build definition? Try clearing it if one is set.
Is this new behaviour in 2.0.0.2? Did the build work before with the load rule specified? If so, what happened to the load rule file?
In any case, the error feedback here could definitely be improved.
I've filed 110713: Improve error feedback when load rules are missing.
Is this new behaviour in 2.0.0.2? Did the build work before with the load rule specified? If so, what happened to the load rule file?
In any case, the error feedback here could definitely be improved.
I've filed 110713: Improve error feedback when load rules are missing.
Thanks, I'll try resetting the load rules on Wednesday as I wont be back to the office till then. The JBE was turned off when we migrated to 2.0 and getting it back on was a low priority since the developers are running the same processes as part of their release cycle (among other reasons).
I'll post back for the results, and thanks for filing the message clarification enhancement. :)
ciao!
I'll post back for the results, and thanks for filing the message clarification enhancement. :)
ciao!
Glad to hear. Could you check the following:
- select the load rules file
- choose File > Properties > Jazz Source Control
- expand the 'show UUIDs' section at the bottom
- check whether the item id is the same as the one it complained about not being able to find before: _mAmlYPNdEd2FwJTraqTVkA
If not, the question is how the file got a new item id. If you just migrated the DB normally, item ids should not have been reassigned. If you did a file-based export/import, then they would be different.
Thanks
- select the load rules file
- choose File > Properties > Jazz Source Control
- expand the 'show UUIDs' section at the bottom
- check whether the item id is the same as the one it complained about not being able to find before: _mAmlYPNdEd2FwJTraqTVkA
If not, the question is how the file got a new item id. If you just migrated the DB normally, item ids should not have been reassigned. If you did a file-based export/import, then they would be different.
Thanks