scm.exe throws CLIClientException
Serge Blokhin (26●6●11)
| asked Nov 01 '13, 2:33 p.m.
retagged Dec 16 '13, 4:10 p.m. by David Lafreniere (4.8k●7)
i am running scm.exe status command and it throws an exception:
Unexpected exception
com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Failure when connecting to: http://127.0.0.1:2082/
service/com.ibm.team.filesystem.client.rest.IFilesystemRestClient/RegisteredSandboxes??computeFully=true
at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:715)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:53)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:534)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:356)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:125)
at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41)
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:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
Caused by: com.ibm.team.filesystem.client.restproxy.exceptions.RestTransportException: Failure when connecting to: http:
//127.0.0.1:2082/service/com.ibm.team.filesystem.client.rest.IFilesystemRestClient/RegisteredSandboxes??computeFully=tru
e
at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeRequest(RestInvocationHandler.java:249)
at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeAndReturnResult(RestInvocationHandler.j
ava:221)
at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invokeInternal(RestInvocationHandler.java:368)
at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invoke(RestInvocationHandler.java:311)
at com.sun.proxy.$Proxy0.getRegisteredSandboxes(Unknown Source)
at com.ibm.team.filesystem.cli.core.util.RepoUtil.findWorkspacesInSandbox(RepoUtil.java:1335)
at com.ibm.team.filesystem.cli.core.util.RepoUtil.findWorkspacesInSandbox(RepoUtil.java:1325)
at com.ibm.team.filesystem.cli.core.util.JSONPrintUtil.jsonizePendingChanges(JSONPrintUtil.java:266)
at com.ibm.team.filesystem.cli.core.util.PendingChangesUtil.printPendingChanges(PendingChangesUtil.java:400)
at com.ibm.team.filesystem.cli.client.internal.subcommands.StatusCmd.run(StatusCmd.java:133)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
... 17 more
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:179)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:229)
at java.io.BufferedInputStream.read(BufferedInputStream.java:248)
at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreaded
HttpConnectionManager.java:1413)
at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeRequest(RestInvocationHandler.java:236)
... 27 more
pretty much all other commands give the same error...
lscm.bat does not give and output at all...
any suggestions?
Thanks
Serge
PS:
in case it helps:
C:\Documents and Settings\build>scm.exe -v
com.ibm.team.filesystem.cli.client, version 3.1.300.v20130426_0115
Provides Subcommands:
load, login, logout, create, create/workspace, create/baseline,
create/changeset, create/snapshot, create/component, create/loadrules,
create/stream, changeset, changeset/comment, changeset/complete,
changeset/current, changeset/relocate, changeset/associate,
changeset/disassociate, changeset/suspend, changeset/resume,
changeset/discard, changeset/extract, changeset/locate, change-target,
change-target/workspace, change-target/component,
change-target/unset-workspace, list, list/workspaces, list/projectareas,
list/teamareas, list/streams, list/components, list/remotefiles,
list/credentials, list/daemons, list/snapshots, list/locks, list/properties,
list/changes, list/users, list/baselines, list/changesets, list/states,
list/flowtargets, list/preferences, checkin, accept, deliver, status,
validate, conflicts, resolve, move, lastmod, share, discard, undo, compare,
history, diff, repair, workspace, workspace/change-target,
workspace/component, workspace/unset, workspace/add-components,
workspace/remove-components, workspace/replace-components, workspace/delete,
workspace/unload, workspace/propertylist, workspace/propertyget,
workspace/propertyset, workspace/add-flowtargets,
workspace/remove-flowtargets, workspace/flowtarget, component,
component/propertylist, component/propertyget, component/propertyset,
baseline, baseline/propertylist, baseline/propertyget, baseline/propertyset,
property, property/list, property/get, property/set, property/remove, lock,
lock/list, lock/acquire, lock/release, annotate, snapshot, snapshot/promote,
snapshot/propertylist, snapshot/propertyget, snapshot/propertyset, refresh,
users, users/set, delete, delete/state-content, changeaccess, extract,
extract/file, debug, debug/fetch, debug/fetch/changeset,
debug/fetch/component, debug/fetch/workspace, debug/fetch/item,
debug/fetch/uri, preference, preference/get, preference/set
com.ibm.team.filesystem.cli.tools, version 3.1.300.v20130503_0103
Provides Subcommands:
tools.verify, tools.validate, tools.echo.stdin, tools.metronome,
tools.pkgtest, tools.configvalue, tools.log, tools.generatehelp, tools.dump,
tools.dump/postprocess
com.ibm.team.filesystem.cli.core, version 3.1.300.v20130426_0115
Provides Subcommands:
daemon, daemon/start, daemon/stop, daemon/deregister, daemon/register
com.ibm.team.rtc.cli.infrastructure, version 3.1.300.v20130425_0448
Provides Subcommands:
help, version
|
Accepted answer
|
Yes the server is up and i am able to connect to it via webclient. The java version is 1.5.0_22
URI i am using as -r parameter is HTTPS. i am not sure why it shows it as HTTP.
guys , i restarted the machine and it started working, so for now i am ok. i will update this question if i run into it again. if you have any suggestions why it might be happening please do. i do see it once in a while especially if my application runs for a long time...
Ralph Schoon selected this answer as the correct answer
Comments 
Ralph Schoon
commented Nov 05 '13, 10:06 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Great that it is working for you now.Maybe a typo?
|
Comments
What Java Version are you using?
The port is also very odd and you use HTTP instead of HTTPS as the repository URI. I am wondering if your URI would work in a browser.