It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,788
×5,999

question asked: Oct 09 '15, 4:53 a.m.
question was seen: 2,724 times
last updated: Oct 11 '15, 8:17 p.m.

Related questions

FAQ - How this Forum works

What should I have done? (NullPointerException)

0
Eddie Breeveld (61●1●25●30) | asked Oct 09 '15, 4:53 a.m.
edited Oct 09 '15, 4:54 a.m.
(RTC 5.0.2, Eclipse Client, Windows 7)

I can't send a picture (not enough reputation) so I'll describe the error dialog. I started an RTC client this morning and got this useless dialog.  I then restarted RTC successfully, but what should I do if it happens again?

Problem occurred
'' has encountered a problem.
An error occurred during "".
[OK] [<<Details]

An internal error occurred during "".
   java.lang.NullPointerException

One answer

Most liked answers|Newest answers|Oldest answers ↑

0
permanent link
Sunil Kumar R (1.1k●1●30●44) | answered Oct 09 '15, 8:41 a.m.
JAZZ DEVELOPER
Hi Eddie, I would look at the .log file from the workspace directory. That log will have more data on the exception you see.

A corrective action might be to start with a fresh workspace location and you could report the issue to IBM Support for further investigation.

Best Regards
Sunil
Comments
Eddie Breeveld commented Oct 09 '15, 8:57 a.m. | edited Oct 11 '15, 8:13 p.m.

Thanks Sunil.  I can't reproduce the problem, but here is the log (incidentally, it is in the .metadata directory, not the workspace directory).  It's still gobbledegook.

!SESSION 2015-10-09 09:17:07.458 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=JRE 1.7.0 IBM J9 2.6 Windows 7 amd64-64 Compressed References 20140627_204598 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR7_20140627_0924_B204598
JIT  - r11.b06_20140409_61252.04
GC   - R26_Java726_SR7_20140627_0924_B204598_CMPRSS
J9CL - 20140627_204598
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Framework arguments:  -product com.ibm.team.concert.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product com.ibm.team.concert.product

!ENTRY org.eclipse.core.jobs 4 2 2015-10-09 09:18:37.406
!MESSAGE An internal error occurred during: "".
!STACK 0
java.lang.NullPointerException
    at com.ibm.team.scm.common.internal.impl.RepositoryProgressMonitorImpl.eSet(RepositoryProgressMonitorImpl.java:373)
    at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1071)
    at com.ibm.team.repository.common.model.impl.ItemImpl.initNew(ItemImpl.java:1083)
    at com.ibm.team.repository.common.model.impl.ItemTypeImpl.createItem(ItemTypeImpl.java:112)
    at com.ibm.team.scm.common.IRepositoryProgressMonitor$RepositoryMonitorFactory.createItem(IRepositoryProgressMonitor.java:47)
    at com.ibm.team.scm.client.internal.WorkspaceManager.refresh(WorkspaceManager.java:2970)
    at com.ibm.team.scm.client.internal.WorkspaceManager.ensureInitialized(WorkspaceManager.java:849)
    at com.ibm.team.scm.client.internal.WorkspaceManager.getWorkspaceConnection(WorkspaceManager.java:870)
    at com.ibm.team.filesystem.internal.rcp.ui.workitems.WorkItemActivationListener.getConnectionFor(WorkItemActivationListener.java:413)
    at com.ibm.team.filesystem.internal.rcp.ui.workitems.WorkItemActivationListener.startListening(WorkItemActivationListener.java:359)
    at com.ibm.team.filesystem.internal.rcp.ui.workitems.WorkItemActivationListener.access$2(WorkItemActivationListener.java:348)
    at com.ibm.team.filesystem.internal.rcp.ui.workitems.WorkItemActivationListener$4.run(WorkItemActivationListener.java:551)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

!ENTRY com.ibm.team.fulltext.common 1 800 2015-10-09 09:19:13.984
!MESSAGE Fulltext:: Server location: C:\RTC_AFM\Main.metadata.plugins\com.ibm.team.fulltext.client\fulltext_index\com.ibm.team.workitem.WorkItem

Donald Nong commented Oct 11 '15, 8:17 p.m.

This is the right .log file. Since you cannot reproduce the issue anymore, it's hard to say what actually went wrong. Judging by the stack trace, the exception was thrown when RTC Eclipse client tried to open the repository connection. It could be that there was a network issue or something, or the Eclipse workspace had some minor corruption.

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.