It's all about the answers!

Ask a question

Cannot list the workspace and change the attribute

samuel wang (321923) | asked Sep 04 '14, 5:02 p.m.
edited Sep 04 '14, 5:30 p.m.
after logged in, created workspace, but not able to list it,
C:\dataRTCAdmin>lscm create workspace RTCWorkspace -s RTCStream -r xxx:9443/ccm
Workspace (9442) "RTCWorkspace" successfully created
C:\dataRTCAdmin>lscm list workspaces  -r xxx:9443/ccm
Problem running 'list workspaces':
Could not find remote item with UUID _LFUbMBmEEeSLMYfsx0M6yw

cannot find anything's id  is  "_LFUbMBmEEeSLMYfsx0M6yw"

and cannot change its attributs:
C:\dataRTCAdmin>lscm -u y set attribute -w RTCWorkspace --ownedby admin -r xxx:9443/ccm
(9442:_GuuUwDRnEeSDhqJ0nWfWLA) "RTCWorkspace"
  Error code: 25
  Error message: Could not find remote item with UUID _LFUbMBmEEeSLMYfsx0M6yw
Problem running 'set attributes':
The property of one or more workspaces was not set.

Donald Nong commented Sep 04 '14, 8:54 p.m.

The same sequence works for me in an RTC 4.0.6 environment. You may need to open a support ticket to get it investigated.

Shashikant Padur commented Sep 04 '14, 11:08 p.m.

Do you have anything in the scm log? I believe there should have been an exception that might point to something. 

samuel wang commented Sep 05 '14, 9:09 a.m.

there are lot of error in ccm.log file,  here is the first error,
2014-09-04 13:26:15,401 [AsynchronousTaskRunner-0 @@ 13:26]  INFO             - Initialize migration task 'Migrate system definitions from EMF to JFS'
2014-09-04 13:26:15,401 [AsynchronousTaskRunner-0 @@ 13:26] ERROR t.internal.registry.AbstractActivationManagerOwner  - The class "" failed to load. The bundle "" could not find the class.
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(

Donald Nong commented Sep 07 '14, 8:46 p.m.

You've got a big problem here. Try to re-deploy JTS and CCM applications. If the problem persists, contact Support to open a PMR.

Lily Wang commented Sep 07 '14, 9:40 p.m.

The log you pasted is not relevant to the issue. Per defect this error in ccm.log can be ignored.

But I do agree with Donald that you may need to contact support to investigate the scm problem.

Be the first one to answer this question!

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.