Skip to Content
0
Former Member
Jan 22, 2009 at 06:59 AM

Error on deploying repository service

50 Views

Hi,

I developed a custom repository service. Upon deploying this (via nwds, quick par upload), I'm seeing a host of error msgs in the default trace:

startup failed : class=com.sapportals.wcm.repository.manager.cm.CmRepositoryManager, uri=crt://runtime/repository_managers/<some RM name>, exception: com.sapportals.wcm.crt.component.StartupException: Configuration exception: Missing attribute: localroot, configuration node = component-config, location... [see details]

CmSystem startUp() triggered by this stack: java.lang.Exception: Exception used to dump stacktrace

at com.sapportals.wcm.repository.runtime.CmSystem.getCurrentStacktrace(CmSystem.java:776)

at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:190)... [see details]

Repository framework startup was not triggered by knowledgemanagement portal service. (Either because hot-deployment occurred or because a faulty custom KM component triggered the startup.)

exception occured when trying to unregister RID generator - com.sapportals.wcm.repository.ResourceException: Failed to access the component instance: already shut down: class=com.sapportals.wcm.service.urlgenerator.URLGenerator, uri=crt://runtime/services/URLGeneratorService

at com.sapportals.wcm.repository.ResourceException.fillInStackTrace(ResourceException.java:399)

Failed to access the component instance: already shut down: class=com.sapportals.wcm.service.urlgenerator.URLGenerator, uri=crt://runtime/services/URLGeneratorService com.sapportals.wcm.crt.component.ComponentException: Failed to access the component instance: already shut down: class=com.sapportals.wcm.service.urlgenerator.URLGenerator, uri=crt://runtime/services/URLGeneratorService

at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:325)

Other than restarting the server, how can I troubleshoot this? I'm not sure what to make out of the above errors, there was an error in registering the Repository service etc..

In addition, I added logger statements, but there's no sign of them in the default trace, looks like the repository service was not even instantiated.

Also, what are the best practices for deployment without running into errors such as above? During development, deploying from nwds is always easier and quicker, but hv been reading otherwise for "hot deployments" not being supported for kmc objects.

Appreciate any pointers on the above. Thanks!

~Prachi