It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,880
×6,037

question asked: Oct 15 '12, 1:06 p.m.
question was seen: 3,159 times
last updated: Oct 17 '12, 1:51 p.m.

Related questions

NPE When Opening Sprint Plan

0
Chris Barlock (188●1●47●38) | asked Oct 15 '12, 1:06 p.m.
I'm getting an NPE when I open our current sprint plan and click on the Planned Items tab, or when I click the Edit button under the View As selection on the Planned Items:

java.lang.NullPointerException
    at com.ibm.team.apt.internal.common.time.TimespanIterator.<init>(TimespanIterator.java:59)
    at com.ibm.team.apt.internal.common.WorktimeScheduler.calcutateWorkingTime(WorktimeScheduler.java:117)
    at com.ibm.team.apt.internal.client.ItemSequenceManager.calculateWorkTime(ItemSequenceManager.java:195)
    at com.ibm.team.apt.internal.ide.ui.editor.outliner.OwnerGadget$NodeContent.<init>(OwnerGadget.java:109)
    at com.ibm.team.apt.internal.ide.ui.editor.outliner.OwnerGadget.<init>(OwnerGadget.java:197)
    at com.ibm.team.apt.internal.ide.ui.editor.outliner.PlanEditorGadgetFactory$OwnerElementGadgetCreator.createGadget(PlanEditorGadgetFactory.java:68)
    at com.ibm.team.apt.internal.ide.ui.common.GadgetFactory.createGadget(GadgetFactory.java:46)
    at com.ibm.team.apt.internal.ide.ui.common.model.OutlineModelViewer.doUpdateItem(OutlineModelViewer.java:118)
    at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:113)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
    at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
    at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1033)
    at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
    at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
    at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167)
    at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:848)
    at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2773)
    at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1923)
    at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1898)
    at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1848)
    at com.ibm.team.apt.internal.ide.ui.editor.outliner.PlanItemOutlineViewer.internalRefresh(PlanItemOutlineViewer.java:111)
    at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1841)
    at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:1508)
    at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
    at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
    at com.ibm.team.apt.internal.ide.ui.widgets.outliner.OutlineViewer.preservingSelection(OutlineViewer.java:144)
    at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1506)
    at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:537)
    at com.ibm.team.apt.internal.ide.ui.editor.outliner.PlanItemOutlineViewer.refresh(PlanItemOutlineViewer.java:67)
    at com.ibm.team.apt.internal.ide.ui.common.model.RefreshEntryRunnable.doRun(RefreshEntryRunnable.java:32)
    at com.ibm.team.apt.internal.ide.ui.common.model.OutlineModelViewerRunnable$1.run(OutlineModelViewerRunnable.java:48)
    at com.ibm.team.apt.internal.ide.ui.common.model.OutlineModelViewerRunnable$1.run(OutlineModelViewerRunnable.java:1)
    at com.ibm.team.apt.internal.ide.ui.common.model.OutlineModel.readModel(OutlineModel.java:384)
    at com.ibm.team.apt.internal.ide.ui.common.model.OutlineModelViewerRunnable.run(OutlineModelViewerRunnable.java:46)
    at com.ibm.team.apt.internal.ide.ui.common.model.OutlineModel$5.run(OutlineModel.java:437)
    at com.ibm.team.apt.internal.ide.ui.util.UI.exec(UI.java:38)
    at com.ibm.team.apt.internal.ide.ui.util.UI.syncExec(UI.java:26)
    at com.ibm.team.apt.internal.ide.ui.common.model.OutlineModel.updateModel(OutlineModel.java:433)
    at com.ibm.team.apt.internal.ide.ui.common.model.OutlineModel.executeUnlocked(OutlineModel.java:394)
    at com.ibm.team.apt.internal.ide.ui.editor.OutlinePageSettingsListener$4.run(OutlinePageSettingsListener.java:159)
    at com.ibm.team.apt.internal.ide.ui.util.UI$1.run(UI.java:49)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
    at java.lang.reflect.Method.invoke(Method.java:613)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

Session data:
eclipse.buildId=unknown
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows 7 x86-32 j9vmwi3223ifx-20100511 (JIT enabled)
J9VM - 20100509_57823_lHdSMr
JIT  - 20091016_1845ifx7_r8
GC   - 20091026_AA
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -product com.ibm.team.concert.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -data C:\D\eclipse\workspaces\rtc_ccm -product com.ibm.team.concert.product

The problem happens in my Eclipse RTC 3.0.1.3 client or in another environment which is the Eclipse Juno Java EE bundle in which I've installed RTC 3.0.1.3 from a local P2 repository.  I even created a new clean workspace and the problem persists.  Others on the team don't see this error, so I think it is something on my system, but no clue what.  Thoughts?

Chris

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Daniel Pool (264●4) | answered Oct 15 '12, 1:39 p.m.
JAZZ DEVELOPER
Hi Chris, The supported versions of eclipse for 3.0.1.3 are:
* Eclipse SDK 3.6, 3.6.1, 3.6.2
* Eclipse SDK 3.5.2 [Bundled]

You can read more at:

I recommend you try a supported version and see if the problem goes away.
Comments
Chris Barlock commented Oct 15 '12, 1:48 p.m.

I could do that, but the problem happens for me if I use the pure Eclipse 3.0.1.3 RTC client.  Could it be that by using an unsupported Eclipse SDK and then pointing the Eclipse RTC client at this workspace, that something is screwed up in the workspace?

Chris
0
permanent link
Daniel Pool (264●4) | answered Oct 15 '12, 2:11 p.m.
JAZZ DEVELOPER
Chris,

I don't know how sharing a workspace across multiple versions of Eclipse works. So that could be an issue. But can try viewing this in the web client? Maybe that will give a clue as to what is going on here.

Daniel
Comments
Chris Barlock commented Oct 15 '12, 2:55 p.m.

The web client doesn't show any problems, though I'm not sure if there is any underlying Java that could throw an NPE.  The requirements you pointed me to list the Eclipse 3.6.x SDK.  Does that mean just the "base 3.6.x. SDK" or does it include any of the bundles (like the Java EE bundle I want to use) based on the base SDK?

Chris

Daniel Pool commented Oct 15 '12, 3:54 p.m.
JAZZ DEVELOPER

I think you should be able to use the Java EE version. I see a change in the 3.0.1.4 eclipse client that might solve the problem you are having. Is there any chance other teammates might be using the newer client?

Chris Barlock commented Oct 15 '12, 9:04 p.m.

I have the same problem with the 3.6.2 Java EE version.  Almost no chance my teammates are using the newer client.  I'm usually the one on the bleeding edge!

Everything I've seen says that the client version must match the server version.  Any problems if I use the 3.0.1.4 client with a 3.0.1.3 server?  (Our next server move is going to be 4.0, I think sometime in November.)

I started this process by trying to install some of the Java EE bundle packages into RTC Eclipse client, but ran into all kinds of missing prereqs.  Could easily be because I just grabbed the current version of those packages, not recognizing the Eclipse 3.6.x limitation.  The installation of RTC into the Java EE bundle worked fine and it is interesting that this NPE didn't happen right away.  I've only seen it with our current sprint plan, which makes me think something in that plan triggers it.  Daniel,  any hints from the line where the NPE occurs?

Chris

Chris Barlock commented Oct 15 '12, 9:05 p.m.

Oh, and if it matters, I'm using the 64-bit Windows version of all these Eclipse installations.

Chris

Chris Barlock commented Oct 17 '12, 1:51 p.m.

I opened defect 237180, since I can reproduce this with the Eclipse 3.6.2 Java EE bundle.

Your answer

Register or 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.