It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,624
×5,939
×112
×1

question asked: Nov 04 '18, 12:56 p.m.
question was seen: 1,358 times
last updated: Nov 08 '18, 12:27 p.m.

Related questions

FAQ - How this Forum works

scm create workspace gives CLIClientException

0
Robin Norberg (11●2) | asked Nov 04 '18, 12:56 p.m.
Hi!

I can't seem to figure out why this simple command is causing an issue?
I'm trying to create a new workspace called "abc", by fetching an existing stream. It doesn't seem to matter which order i run the command parameters in.
I've only tried it with --integratedWindows, since that's our only allowed option for connecting.

Thanks!

C:\Teamconcert\scmtools\eclipse>scm version
Build Id: RTC-CLIENT-I20160323-2215
Version: 6.0.2

Works (workspace not related to stream): 
C:\Teamconcert\scmtools\eclipse>scm create workspace "abc" -r <repo> --integratedWindows
Workspace (2048) "abc" successfully created.
Component (2049) "abc Default Component" successfully created.

Causes CLIClientException: 
create workspace abc -r <repo> --integratedWindows -u <user> -s <streamName>

C:\Teamconcert\scmtools\eclipse>scm create workspace "abc" -r <repo> --integratedWindows -u <user> -s <streamName> 
Unexpected exception
com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error
        at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:782)
        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:601)
        at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370)
        at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130)
        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(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        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)
Caused by: java.lang.NullPointerException
        at com.ibm.team.filesystem.cli.core.util.RepoUtil.login(RepoUtil.java:753)
        at com.ibm.team.filesystem.cli.core.util.RepoUtil.loginUrlArgAnc(RepoUtil.java:512)
        at com.ibm.team.filesystem.cli.core.util.RepoUtil.loginUrlArgAncestor(RepoUtil.java:662)
        at com.ibm.team.filesystem.cli.client.internal.createcommand.CreateStreamCmd.run(CreateStreamCmd.java:112)
        at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
        ... 16 more
-----------------
.log:
... 16 more
!SESSION 2018-11-04 18:33:03.133 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_72
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  create workspace abc -r <repo> --integratedWindows -u <user> -s <streamName>
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -data @noDefault create workspace abc -r <repo> --integratedWindows -u <user> -s <streamName>
!ENTRY org.eclipse.osgi 2 1 2018-11-04 18:33:04.096
!MESSAGE NLS unused message: ResolveCmd_No_CONFLICTS in: com.ibm.team.filesystem.cli.client.internal.messages
!ENTRY org.eclipse.osgi 2 1 2018-11-04 18:33:04.097
!MESSAGE NLS unused message: ResolveCmd_INVALID_SANDBOX in: com.ibm.team.filesystem.cli.client.internal.messages
!ENTRY org.eclipse.osgi 2 1 2018-11-04 18:33:04.098
!MESSAGE NLS unused message: ResolveCmd_INVALID_SANDBOX_ARGUMENT_1 in: com.ibm.team.filesystem.cli.client.internal.messages
!ENTRY org.eclipse.osgi 2 1 2018-11-04 18:33:04.099
!MESSAGE NLS unused message: ResolveCmd_INVALID_SANDBOX_ARGUMENT_2 in: com.ibm.team.filesystem.cli.client.internal.messages
!ENTRY org.eclipse.osgi 2 1 2018-11-04 18:33:04.194
!MESSAGE NLS unused message: RepoUtil_NoDeliverableMatchingName in: com.ibm.team.filesystem.cli.core.internal.messages
!ENTRY org.eclipse.osgi 2 0 2018-11-04 18:33:08.136
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.136
!MESSAGE Bundle update@plugins/org.eclipse.ui.navigator.resources_3.4.202.M20101124-0800.jar was not resolved.
!SUBENTRY 2 org.eclipse.ui.navigator.resources 2 0 2018-11-04 18:33:08.136
!MESSAGE Missing required bundle org.eclipse.ltk.core.refactoring_[3.5.0,4.0.0).
!SUBENTRY 2 org.eclipse.ui.navigator.resources 2 0 2018-11-04 18:33:08.136
!MESSAGE Missing required bundle org.eclipse.ltk.ui.refactoring_[3.5.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.136
!MESSAGE Bundle update@plugins/org.junit_4.8.1.v4_8_1_v20100427-1100/ was not resolved.
!SUBENTRY 2 org.junit 2 0 2018-11-04 18:33:08.136
!MESSAGE Missing required bundle org.hamcrest.core_1.1.0.
!ENTRY org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.core.filesystem.linux.x86.nl1_1.4.0.v201102251823 [220] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.core.filesystem.linux.x86.nl2a_1.4.0.v201104190813 [221] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.core.filesystem.linux.x86.nl2_1.4.0.v201102251823 [222] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.core.filesystem.win32.x86.nl1_1.1.201.v201102251823 [226] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.core.filesystem.win32.x86.nl2a_1.1.201.v201104190813 [227] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.core.filesystem.win32.x86.nl2_1.1.201.v201102251823 [228] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.core.filesystem.zos.s390x_3.0.1.v20151120_1440 [230] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.core.filesystem.zos.s390_3.0.1.v20151120_1440 [231] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.ui.navigator.resources.nl1_3.4.202.v201102251823 [417] was not resolved.
!SUBENTRY 2 org.eclipse.ui.navigator.resources.nl1 2 0 2018-11-04 18:33:08.141
!MESSAGE Missing host org.eclipse.ui.navigator.resources_[3.4.0,3.5.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.ui.navigator.resources.nl2a_3.4.202.v201104190813 [418] was not resolved.
!SUBENTRY 2 org.eclipse.ui.navigator.resources.nl2a 2 0 2018-11-04 18:33:08.141
!MESSAGE Missing host org.eclipse.ui.navigator.resources_[3.4.0,3.5.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.ui.navigator.resources.nl2_3.4.202.v201102251823 [419] was not resolved.
!SUBENTRY 2 org.eclipse.ui.navigator.resources.nl2 2 0 2018-11-04 18:33:08.141
!MESSAGE Missing host org.eclipse.ui.navigator.resources_[3.4.0,3.5.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.eclipse.ui.navigator.resources_3.4.202.M20101124-0800 [420] was not resolved.
!SUBENTRY 2 org.eclipse.ui.navigator.resources 2 0 2018-11-04 18:33:08.141
!MESSAGE Missing required bundle org.eclipse.ltk.core.refactoring_[3.5.0,4.0.0).
!SUBENTRY 2 org.eclipse.ui.navigator.resources 2 0 2018-11-04 18:33:08.141
!MESSAGE Missing required bundle org.eclipse.ltk.ui.refactoring_[3.5.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2018-11-04 18:33:08.141
!MESSAGE Bundle org.junit_4.8.1.v4_8_1_v20100427-1100 [463] was not resolved.
!SUBENTRY 2 org.junit 2 0 2018-11-04 18:33:08.141
!MESSAGE Missing required bundle org.hamcrest.core_1.1.0.
!ENTRY org.eclipse.osgi 4 0 2018-11-04 18:33:08.143
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error
  at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:143)
   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(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 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)
Caused by: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error
    at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:782)
  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:601)
   at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370)
   at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130)
   ... 13 more
Caused by: java.lang.NullPointerException
   at com.ibm.team.filesystem.cli.core.util.RepoUtil.login(RepoUtil.java:753)
 at com.ibm.team.filesystem.cli.core.util.RepoUtil.loginUrlArgAnc(RepoUtil.java:512)
    at com.ibm.team.filesystem.cli.core.util.RepoUtil.loginUrlArgAncestor(RepoUtil.java:662)
   at com.ibm.team.filesystem.cli.client.internal.createcommand.CreateStreamCmd.run(CreateStreamCmd.java:112)
 at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
 ... 16 more

3 answers

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Shashikant Padur (4.2k●2●7) | answered Nov 05 '18, 5:18 a.m.
JAZZ DEVELOPER

Please contact support so that they could find out more details and help debug the issue. 
0
permanent link
Shashikant Padur (4.2k●2●7) | answered Nov 04 '18, 10:50 p.m.
JAZZ DEVELOPER

The difference between the two commands apart from the -s option is the -u option. As per the command help you should not specify the -u option when --integratedWindows option is specified as it takes the windows credentials (username & password).

Ideally the command should have thrown an error informing the user not to input the username.

Comments
Robin Norberg commented Nov 05 '18, 2:25 a.m.

 Well, sure. But even if i supply the -u option it's ignored regardless so it doesn't matter.


See my elaborate answer in my own reply below (character limit)

0
permanent link
Robin Norberg (11●2) | answered Nov 05 '18, 2:24 a.m.
edited Nov 05 '18, 2:47 a.m.
(Regardless if i use --integratedWindows or -u, the problem still remain)

Both of these works even with user id: 

scm create workspace "abcde" -r https://<repo>/ --integratedWindows -u <userid>
Workspace (2051) "abcde" successfully created.
Component (2052) "abcde Default Component" successfully created.

scm create workspace "abcdef" -r https://<repo>/ --integratedWindows
Workspace (2053) "abcdef" successfully created.
Component (2054) "abcdef Default Component" successfully created.

If i try to create a workspace with a non-existing stream: 

scm create workspace "abcdefg" -r https://<repo>/ -s "xyz"
Problem running 'create workspace':
Unmatched workspace/stream "xyz"

Trying to create it from existing streams however throws an exception (with or without --integratedWindows or -u tag 
scm create workspace "abcdefg" -r https://<repo>/ -s "existingStream"
Unexpected exception
com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error
        at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:782)
        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:601)
        at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370)
        at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130)
        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(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        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)
Caused by: java.lang.NullPointerException
        at com.ibm.team.filesystem.cli.core.util.RepoUtil.login(RepoUtil.java:753)
        at com.ibm.team.filesystem.cli.core.util.RepoUtil.loginUrlArgAnc(RepoUtil.java:512)
        at com.ibm.team.filesystem.cli.core.util.RepoUtil.loginUrlArgAncestor(RepoUtil.java:662)
        at com.ibm.team.filesystem.cli.client.internal.createcommand.CreateStreamCmd.run(CreateStreamCmd.java:112)
        at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
        ... 16 more
Comments
Shashikant Padur commented Nov 05 '18, 3:19 a.m.
JAZZ DEVELOPER

I am not sure what is going on, but could you try running your command with --non-interactive option:

scm --non-interactive create workspace "abcdefg" -r https://<repo>/ -s "existingStream" 

Robin Norberg commented Nov 05 '18, 4:37 a.m. | edited Nov 05 '18, 4:37 a.m.

 Thanks for the suggestion! Unfortunately, the same issue occur.


scm --non-interactive create workspace "abcdef" -r https://<repo>/ -s "existingStream"
Unexpected exception
com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error

Your answer

Register or to post your answer.