Hi
I'm having issues upgrading our production confluence installation from version 4.1.9 to version 4.2.0. I've attempted this twice and both times I've been forced to roll back the upgrade.
The Upgrade in its self is successful and i can log into confluence, however when i request a page i get a browser error indicating that /pages/viewpage.vm cannot be found. In the application log i see the following error:
2012-04-11 13:31:21,738 WARN [http-8280-5] [adaptavist.plm.service.VerificationServiceTrackerCustomizer] addingService PLM Jar file was not signed by PLM Root Certificate, License Service will be unavailable
– referer: http://confluence.us.sagepub.org/dashboard.action | url: /display/SPSI/Alfresco+Installation+on+Ubuntu+10.4 | userName: Fowler | action: viewpage | page: 44237099
2012-04-11 13:31:22,190 ERROR [http-8280-5] [opensymphony.webwork.dispatcher.VelocityResult] doExecute Unable to render Velocity Template, '/pages/viewpage.vm'
– referer: http://confluence.us.sagepub.org/dashboard.action | url: /display/SPSI/Alfresco+Installation+on+Ubuntu+10.4 | userName: Fowler | action: viewpage | page: 44237099
org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource '/pages/viewpage.vm'
...
...
I have macro's (templates) on all my pages that use the adaptivist free plugins, activiated by the Plugin Licensing Manager (PLM). My suspicion is that the WARN statement above means that when the PLM License Service is unavailable, that all the Adaptivis plugins also fail, and ultimately causes the ERROR i see in the logs.
I have also asked the same question on Atlassian Answers where i also attached a full log from a confluence restart and an attempt to access the page.
The Atlassian Answers question can be found here: https://answers.atlassian.com/questions/47138/confluence-4-2-upgrade-adaptivist-plugin-warn-addingservice-plm-jar-file-was-not-signed-by-plm-root-certificate-license-service-will-be-unavailabl
Many thanks
Gavin.
Comments (5)
Apr 11, 2012
Gareth Wilson says:
Thanks for your question. None of our plugins are currently compatible with Conf...Thanks for your question. None of our plugins are currently compatible with Confluence 4.2. We'd recommend removing incompatible plugins prior to upgrade or not upgrading until the required plugins have been upgraded.
Apr 11, 2012
Gavin Fowler says:
Many thanks for the clarification Gareth. I had upgraded our non production env...Many thanks for the clarification Gareth.
I had upgraded our non production environment without issue, which was the cause for my confusion. I refreshed our non production server with the production configuration & data and now the problem can be reproduced in this instance too.
I will now wait until I Adaptivist upgraded their plugins to Confluence 4.2 specification. FYI - the two plugins i use are:
Page Information Tools 2.0.0
Plugin Licensing Manager Plugin 0.6.1
Many thanks for your support.
Gavin.
Apr 13, 2012
Gareth Wilson says:
Thanks for the additional info Gavin. You might like to try using v2.0.1 of Page...Thanks for the additional info Gavin. You might like to try using v2.0.1 of Page Info tools, as this involves an update which should get around the PLM signing issue you experienced.
Apr 13, 2012
Gavin Fowler says:
Hey Gareth, Pure luck, but i noticed that the plugin Page Information (2.0.1) ...Hey Gareth,
Pure luck, but i noticed that the plugin Page Information (2.0.1) was available about 20 minutes ago. I've applied the update to my non production system, and upgrade from 4.1.9 to 4.2. I can confirm that previously reported issues has been resolved with version 2.0.1 of the plugin.
Many thanks for the follow up and the speedy turn around for resolve. Much appreciated!!
Gavin.
Apr 13, 2012
Gareth Wilson says:
Great! I'm glad this sorted your problem.Great! I'm glad this sorted your problem.