cancel
Showing results for 
Search instead for 
Did you mean: 

Records Management does not appear after installation

jeeko
Champ in-the-making
Champ in-the-making
Hi,

I have installed both AMP files and deployed and started alfresco and I see no Records Space appearing under company home. I use version 3.4.d.
After starting the share I do see this in the log of the share:

SEVERE: The web application [/share] created a ThreadLocal with key of type [null] (value [org.springframework.extensions.webscripts.processor.FTLTemplateProcessor$NonBlockingObjectWrapper$1@71304a7c]) and a value of type [freemarker.template.DefaultObjectWrapper] (value [freemarker.template.DefaultObjectWrapper@2d588db6]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
24-mei-2011 9:38:53 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
SEVERE: The web application [/share] created a ThreadLocal with key of type [null] (value [org.springframework.extensions.webscripts.processor.FTLTemplateProcessor$NonBlockingObjectWrapper$1@71689bf1]) and a value of type [freemarker.template.DefaultObjectWrapper] (value [freemarker.template.DefaultObjectWrapper@10bfbefc]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository.
24-mei-2011 9:38:54 org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8090
24-mei-2011 9:39:37 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8090
24-mei-2011 9:39:37 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 844 ms
24-mei-2011 9:39:37 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
24-mei-2011 9:39:37 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.29
24-mei-2011 9:39:37 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive share.war
09:39:56,329  INFO  [extensions.webscripts.DeclarativeRegistry] Registered 305 Web Scripts (+0 failed), 315 URLs
09:39:56,331  INFO  [extensions.webscripts.DeclarativeRegistry] Registered 8 Package Description Documents (+0 failed)
09:39:56,331  INFO  [extensions.webscripts.DeclarativeRegistry] Registered 0 Schema Description Documents (+0 failed)
09:39:56,691  INFO  [extensions.webscripts.AbstractRuntimeContainer] Initialised Spring Surf Container Web Script Container (in 6850.048ms)
09:39:56,726  INFO  [extensions.webscripts.TemplateProcessorRegistry] Registered template processor freemarker for extension ftl
09:39:57,180  INFO  [extensions.webscripts.ScriptProcessorRegistry] Registered script processor javascript for extension js
09:39:58,219  INFO  [extensions.webscripts.TemplateProcessorRegistry] Registered template processor freemarker for extension ftl
09:39:58,265  INFO  [extensions.webscripts.ScriptProcessorRegistry] Registered script processor javascript for extension js
09:39:59,441  INFO  [extensions.webscripts.TemplateProcessorRegistry] Registered template processor freemarker for extension ftl
09:39:59,446  INFO  [extensions.webscripts.ScriptProcessorRegistry] Registered script processor javascript for extension js
24-mei-2011 9:39:59 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8090
24-mei-2011 9:39:59 org.apache.catalina.startup.Catalina start
INFO: Server startup in 22253 ms

Can  anybody help me out here?

Jeeko
6 REPLIES 6

mrogers
Star Contributor
Star Contributor
You can ignore that scary sounding error !

Have you created the site through the RM Dashlet?

http://wiki.alfresco.com/w/images/6/62/Installing_and_Configuring_Alfresco_ECM_Community_Edition_3_2...

jeeko
Champ in-the-making
Champ in-the-making
No I didn't but now I have added the RM dashlet and created the site and see it in My Sites in the share!

Thanks! Now it works.  Smiley Very Happy

sor
Champ in-the-making
Champ in-the-making
Ok, banging my head against this for a day now and finally decided to join the forum.  I've been trying to figure out how to create a document expiration policy such that documents will be reviewed/updated regularly. I understand this is a part of the Records Management plugin, but am unable to find it. Most of the information I've come across seems outdated. I am using 4.0.a and do not find Records Management as an option during install, nor do I find alfresco-dod5015-share.amp anywhere. The online manual refers to a RM dashlet as though I should automatically have it. Help would be appreciated.

mikeh
Star Contributor
Star Contributor
Ok, banging my head against this for a day now and finally decided to join the forum.  I've been trying to figure out how to create a document expiration policy such that documents will be reviewed/updated regularly. I understand this is a part of the Records Management plugin, but am unable to find it. Most of the information I've come across seems outdated. I am using 4.0.a and do not find Records Management as an option during install, nor do I find alfresco-dod5015-share.amp anywhere. The online manual refers to a RM dashlet as though I should automatically have it. Help would be appreciated.
Due to the wide-reaching refactoring of Share during the 4.0 development cycle, further work is needed to the RM module before it is compatible. We are also using this time to rework the module to address some of the limitations (e.g. strict hierarchy). This work won't be complete before the end of the year.

For now, you'll have to use 3.4 if you need Records Management.

Thanks,
Mike

sor
Champ in-the-making
Champ in-the-making
Thanks. I had considered that it might not be fully featured yet, but had a hard time finding a 3.4 download.  If Record Management is going to eventually be available in 4+ I think it would probably be better to start with 4.0.a than to have to worry about migrating from 3.4 to 4.0 later on, no? As long as I can add record management say in the next year or so that would work for us.