IllegalArgumentException when opening a project area in Eclipse editor
Recently a customer reported receiving this message when opening a project area for editing in the Eclipse RTC
client:
An internal error occurred during: "Loading"
In the details was a stack trace that started with:
java.lang.IllegalArgumentExcep
tion
at com.ibm.team.process.internal.
client.workingcopies.
IterationStructureWorkingCopy$
LocalWorkingCopyManager.getWor
kingCopy
(IterationStructureWorkingCopy
.java:143)
at com.ibm.team.process.internal.
client.workingcopies.
IterationStructureWorkingCopy.
findCurrentState
(IterationStructureWorkingCopy
.java:648)
at com.ibm.team.process.internal.
client.workingcopies.
IterationStructureWorkingCopy.
computeCurrentIterations
(IterationStructureWorkingCopy
.java:369)
at com.ibm.team.process.internal.
client.workingcopies.
IterationStructureWorkingCopy.
computeIterationInformation
(IterationStructureWorkingCopy
.java:356)
at com.ibm.team.process.internal.
client.workingcopies.
IterationStructureWorkingCopy.
access$2(IterationStructureWor
kingCopy.
java:352)
at com.ibm.team.process.internal.
client.workingcopies.
IterationStructureWorkingCopy$
1.execute(IterationStructureWo
rkingCopy.
java:302)
at com.ibm.team.process.internal.
client.workingcopies.ExecUtil.
asyncExec
(ExecUtil.java:32)
What caused the error?
client:
An internal error occurred during: "Loading"
In the details was a stack trace that started with:
java.lang.IllegalArgumentExcep
at com.ibm.team.process.internal.
IterationStructureWorkingCopy$
(IterationStructureWorkingCopy
at com.ibm.team.process.internal.
IterationStructureWorkingCopy.
(IterationStructureWorkingCopy
at com.ibm.team.process.internal.
IterationStructureWorkingCopy.
(IterationStructureWorkingCopy
at com.ibm.team.process.internal.
IterationStructureWorkingCopy.
(IterationStructureWorkingCopy
at com.ibm.team.process.internal.
IterationStructureWorkingCopy.
java:352)
at com.ibm.team.process.internal.
IterationStructureWorkingCopy$
java:302)
at com.ibm.team.process.internal.
(ExecUtil.java:32)
What caused the error?
One answer
The exception occurred because the iteration that was set as the current iteration for one of the development lines was not listed as a valid iteration for the project area.
To get around the exception, the user set a different iteration as the current iteration by editing the project area in the web client. The project area editor in the web does not do the same check as the Eclipse client, so it did not raise an error when the project was opened.
Further investigation showed that at some point several iterations had been removed from the iteration structure associated with the project area. The iteration that was listed as the current iteration was one of them. It is not clear how this happened.
Ruby
Martha (Ruby) Andrews
Jazz Foundation L3 Developer
To get around the exception, the user set a different iteration as the current iteration by editing the project area in the web client. The project area editor in the web does not do the same check as the Eclipse client, so it did not raise an error when the project was opened.
Further investigation showed that at some point several iterations had been removed from the iteration structure associated with the project area. The iteration that was listed as the current iteration was one of them. It is not clear how this happened.
Ruby
Martha (Ruby) Andrews
Jazz Foundation L3 Developer