CLM 4.0.1 to 5.0.2: Fails on Initialize/Publish RM
Hello,
I'm upgrading from CLM 4.0.1 on Windows Server 2008 to CLM 5.0.2 on Linux SUSE 11. This installation of CLM started at 2.x and has been upgraded to CLM 4.x in the past.
I followed the IBM upgrade guide, upgraded the applications, started them and navigated to the initialize URL for RM. I checked the application logs and found the following errors:
rm.log
2016-03-14 19:46:09,610 [ WebContainer : 0] WARN team.fulltext.service.internal.FullTextServiceImpl - CRJAZ8191W: The full-text index location is not set
2016-03-14 19:46:10,274 [ WebContainer : 0] ERROR ompatibility.internal.JtsConfigurationStateService - CRJAZ2679E The JTS version could not be determined because the JTS rootservices document at "https://testrtc.xxxxxxxxxxxxx.com:9443/jts/rootservices" could not be fetched or does not have an about services URI.
2016-03-14 19:46:10,494 [ WebContainer : 1] INFO ing.server.core.repository.RepositoryAccessManager - CRRRS9938I Repository state is: INITIALIZING
2016-03-14 19:46:10,530 [ WebContainer : 1] INFO com.ibm.rdm.fronting.server - CRRRS9302I IConfig loading.
2016-03-14 19:46:10,536 [ WebContainer : 1] INFO com.ibm.rdm.fronting.server.common.views.ViewNs - CRRRS4100I Initialise(https://testrm.xxxxxxxx.com:9443/rm)
2016-03-14 19:46:10,536 [ WebContainer : 1] INFO com.ibm.rdm.fronting.server - CRRRS9302I IConfig loading.
2016-03-14 19:46:10,540 [ WebContainer : 1] INFO com.ibm.rdm.fronting.server.common.views.ViewNs - CRRRS4100I Initialise(https://testrm.xxxxxxx.com:9443/rm)
2016-03-14 19:46:10,541 [ WebContainer : 1] ERROR ibm.rdm.fronting.server.rrs.publish.PublishService - CRRRS1007E A problem occurred in the Requirements Management (RM) server: Entry [ce4fa5ecc841ae20]
com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalStateException: value is absent
jazz.log, jts.log and qm.log all have this error
2016-03-14 19:44:12,935 [Component Resolve Thread (Bundle 94)] WARN team.server.monitoring.resources.cache.CacheManager - The free space available "1906668544" in the cache directory is lower than the minimum amount recommended: "2147483648". If monitoring is enabled, it may have an impact on server performance.
Any help with resolving these errors would be greatly appreciated!
Cheers, Cam.
Comments
Cameron McKay
Mar 14 '16, 11:20 p.m.Your right, Donald Nong. This is on a test environment and I had performed a server rename prior to the upgrade. Thanks for the suggestion.