Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

com.ibm.team.repository.common.StaleDataException

When would this happen? The description says: The history for 'Workspace 'MyWorkspace':Component 'Custom MyTool Component'' is more recent in the repository than the version you have. This usually means that another client has modified it first. Please refresh and try again.

I am sure nobody apart from me has delivered anything to stream and my workspace is fully synchronized and refreshed. I see no pending changes. Why do I still see this? If I request a personal build, everything is fine.

0 votes



3 answers

Permanent link
vvtesh wrote:
When would this happen? The description says: The history for
'Workspace 'MyWorkspace':Component 'Custom MyTool Component'' is more
recent in the repository than the version you have. This usually means
that another client has modified it first. Please refresh and try
again.

I am sure nobody apart from me has delivered anything to stream and my
workspace is fully synchronized and refreshed. I see no pending
changes. Why do I still see this? If I request a personal build,
everything is fine.

This error would not be caused by other clients making normal deliveries
to your stream. It might be explained by the definition of the
component having changed. Is it possible that you have used another
client to edit the component?

Once you refresh, does the error go away or does it reoccur?

Thanks
Craig Chaney
Jazz server team

0 votes


Permanent link
When would this happen? The description says: The history for 'Workspace 'MyWorkspace':Component 'Custom MyTool Component'' is more recent in the repository than the version you have. This usually means that another client has modified it first. Please refresh and try again.

I am sure nobody apart from me has delivered anything to stream and my workspace is fully synchronized and refreshed. I see no pending changes. Why do I still see this? If I request a personal build, everything is fine.


Hi

I saw this at one of my customers recently. They were using an external build tool (mavern) and we think that might have touched a file. What we did to fix it was scrap the current Eclipse Workspace and repo workspace, and use new ones. This seemed to fix the problem.

anthony

0 votes


Permanent link
I saw this issue on Solaris. The problem turned out to be 2 zombie processes that were lingering on. Killing them solved the problem.

0 votes

Your answer

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Apr 24 '09, 5:07 a.m.

Question was seen: 6,482 times

Last updated: Apr 24 '09, 5:07 a.m.

Confirmation Cancel Confirm