Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Confluence failing to open with error following a failed XML restore

Ajay Madar May 31, 2018

Hello I have just tried a XML restore from our Production site (v5.9.8) into our test site (v6.9.0) but the restore failed and now when I access Confluence  I get an error as follows:

 

org.apache.velocity.exception.MethodInvocationException: Invocation of method 'isShowSignUp' in class com.atlassian.confluence.user.actions.LoginAction threw exception java.lang.NullPointerException: Application cannot be null at /login.vm[line 6, column 28]
    at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337)

caused by: java.lang.NullPointerException: Application cannot be null
    at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:226)

 

I found this article online "https://confluence.atlassian.com/confkb/confluence-returns-system-error-due-to-invocation-of-method-isshowsignup-in-class-com-atlassian-confluence-user-actions-loginaction-threw-exception-java-lang-nullpointerexception-at-login-vm-693899125.html?_ga=2.97440476.2116427662.1527608717-110770452.1527608717" but my DBA says that the table = cwd_app_dir_mapping does not contain any data.

Regards,

Ajay

1 answer

0 votes
Ajay Madar May 31, 2018

Just to add that when restoring the XML file I got the following error on Confluence>backup & restore page:

com.atlassian.confluence.importexport.ImportExportException: Unable to complete import: XML document structures must start and end within the same entity.

AnnWorley
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 31, 2018

Hi Ajay,

If the objective is to clone Production on the test instance please spin up a new Confluence 5.9.8 on the test server, import the backup from Production and then upgrade the test instance as described in Upgrading Confluence.

The in-product documentation is misleading as it says you can upload a backup "from Confluence 4.0 and later, and space imports from Confluence 5.3 and later."

As recorded in this bug report, the information apppears to be inaccurate:

Inaccurate XML Import documentation and text on Confluence Admin>>Backup and restore

Between Confluence 5.9.x and 6.9.x there have been many schema changes taht can not be anticipated by the older exports. Our doc, Upgrading Confluence mentions:

XML backups should not be used to upgrade Confluence.

Thanks,

Ann

Ajay Madar June 4, 2018

Thanks for the response Ann. We will update our upgrade plan for Confluence accordingly. 

 

Ajay

Aaron Gasperi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 25, 2018

Hi @AnnWorley, I'm running into a similar problem.  I have a Confluence XML export that is at least a year old, but do not have notes as to which version created the export.  I took the approach of installing the most recent version of confluence and attempting an import, but ran into a similar error.  

Would it make sense to:

1) Identify the version of Confluence that output the XML export

2) Install historical version of Confluence.  

3) Perform XML import

4) Upgrade Confluence

If so -- can you give me any tips on how to find out which version of Confluence output an XML Export from the export files?

 

Thank you for your help!

 

Aaron

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events