It's all about the answers!

Ask a question

Check-in History throws java.io.IOException: Unexpected character "60": line 1, column 1


SEC Servizi (93622141) | asked Oct 23 '18, 4:22 a.m.
Any advice on how can we repair it?
com.ibm.team.repository.common.TeamRepositoryException: Unexpected character "60": line 1, column 1
at com.ibm.team.scm.client.content.BasicVersionedContentManager.invokeGetContentStatus(BasicVersionedContentManager.java:1200)
at com.ibm.team.scm.client.content.BasicVersionedContentManager$5.run(BasicVersionedContentManager.java:1072)
at com.ibm.team.scm.client.content.BasicVersionedContentManager$5.run(BasicVersionedContentManager.java:1)
at com.ibm.team.repository.client.internal.TeamRepository$3.run(TeamRepository.java:1324)
at com.ibm.team.repository.common.transport.CancelableCaller.call(CancelableCaller.java:79)
at com.ibm.team.repository.client.internal.TeamRepository.callCancelableService(TeamRepository.java:1319)
at com.ibm.team.scm.client.internal.ScmClientLibraryContext.callCancelableService(ScmClientLibraryContext.java:71)
at com.ibm.team.scm.client.content.BasicVersionedContentManager.getContentStatusChunk(BasicVersionedContentManager.java:1063)
at com.ibm.team.scm.client.content.BasicVersionedContentManager.getContentStatus(BasicVersionedContentManager.java:1017)
at com.ibm.team.scm.client.internal.content.SCMVersionedContentManager.getContentStatus(SCMVersionedContentManager.java:109)
at com.ibm.team.filesystem.rcp.core.internal.changes.util.ChangeSetNodeUtil.getContentDeletedStatus(ChangeSetNodeUtil.java:154)
at com.ibm.team.internal.filesystem.ui.views.history.HistoryView$UpdateStatesJob.repositoryRun(HistoryView.java:230)
at com.ibm.team.repository.rcp.ui.operations.RepositoryOperation.run(RepositoryOperation.java:43)
at com.ibm.team.repository.rcp.ui.operations.RetryQueue.run(RetryQueue.java:146)
at com.ibm.team.repository.rcp.ui.operations.RetryQueue.access$0(RetryQueue.java:124)
at com.ibm.team.repository.rcp.ui.operations.RetryQueue$1.run(RetryQueue.java:42)
at com.ibm.team.repository.rcp.ui.operations.JobRunner.run(JobRunner.java:240)
at com.ibm.team.repository.rcp.ui.operations.JobRunner$1.run(JobRunner.java:63)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.io.IOException: Unexpected character "60": line 1, column 1
at com.ibm.team.repository.common.json.internal.Tokenizer.next(Tokenizer.java:113)
at com.ibm.team.repository.common.json.internal.Parser.parse(Parser.java:30)
at com.ibm.team.repository.common.json.JSONArray.parse(JSONArray.java:148)
at com.ibm.team.scm.client.content.BasicVersionedContentManager.invokeGetContentStatus(BasicVersionedContentManager.java:1163)
... 18 more
Thanks in advance.
Cheers.

Comments
SEC Servizi commented Oct 23 '18, 4:25 a.m.

Ralph Schoon commented Sep 10, 4:03 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

That could be because the RTC API does not work with all the applications any more. I think this is due to an incompatibility introduced in the 6.x authentication changes. 

Accepted answer


permanent link
David Lafreniere (4.2k7) | answered Oct 23 '18, 10:16 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
edited Oct 23 '18, 10:17 a.m.

It looks like there's some unexpected response coming back from the server that's not getting parsed correctly as JSON. I'm not sure there's much that can be answered with this stack trace on its own. It looks like someone may have to investigate this. Can you please raise an escalation with support on this issue if it persists?

Ralph Schoon selected this answer as the correct answer

Comments
SEC Servizi commented Oct 24 '18, 3:22 a.m. | edited Oct 24 '18, 10:07 a.m.
It looks like there's some unexpected response coming back from the server that's not getting parsed correctly as JSON.

Yeah, but that JSON is created by SCM from com.ibm.team.scm.client.content.BasicVersionedContentManager, so it could be there are some repository data corrupted on database?

Thanks in advance.
Cheers.


David Lafreniere commented Oct 24 '18, 10:09 a.m. | edited Oct 24 '18, 10:10 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

I agree that could be the case. Without investigation it would be hard to speculate why/how this is happening though, or what to do to correct it. Support should help resolve this issue via an escalation.

Your answer


Register or to post your answer.