Hello,
I am working on developing a space blueprint, having done this successfully for a client using an older version of Confluence (6.7ish). However, I have noticed that, upon uninstalling or disabling the space blueprint plugin during testing, clicking on "Create Space" results in "Unknown Server Error". Examination of the logfiles reveals the following occurs each time the "Create Space" link is clicked:
[INFO] [talledLocalContainer] 2019-02-07 13:05:47,823 WARN [http-nio-1990-exec-3] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions:
[INFO] [talledLocalContainer] ->[PluginReadWriteTx]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #1303486283)
[INFO] [talledLocalContainer] -- referer: http://desktop-3msduqn:1990/confluence/plugins/servlet/upm | url: /confluence/rest/create-dialog/1.0/space-blueprint/dialog/web-items | traceId: 6e82d9a1ee1790af | userName: admin
Steps to reproduce:
git clone git@bitbucket.org:atlassian_tutorial/confluence-space-blueprint.git
atlas-run
atlas-clean
<properties>to this:
<confluence.version>6.7.1</confluence.version>
<confluence.data.version>6.7.1</confluence.data.version>
<amps.version>6.3.15</amps.version>
<plugin.testrunner.version>1.2.3</plugin.testrunner.version>
<atlassian.spring.scanner.version>1.2.13</atlassian.spring.scanner.version>
<!-- This key is used to keep the consistency between the key in atlassian-plugin.xml and the key to generate bundle. -->
<atlassian.plugin.key>${project.groupId}.${project.artifactId}</atlassian.plugin.key>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>
</properties>
<properties>
<confluence.version>6.14.0</confluence.version>
<confluence.data.version>6.14.0</confluence.data.version>
<amps.version>6.3.15</amps.version>
<plugin.testrunner.version>1.2.3</plugin.testrunner.version>
<atlassian.spring.scanner.version>1.2.13</atlassian.spring.scanner.version>
<!-- This key is used to keep the consistency between the key in atlassian-plugin.xml and the key to generate bundle. -->
<atlassian.plugin.key>${project.groupId}.${project.artifactId}</atlassian.plugin.key>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>
</properties>
[INFO] [talledLocalContainer] 2019-02-07 15:35:17,015 WARN [http-nio-1990-exec-8] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions:
[INFO] [talledLocalContainer] ->[PluginReadWriteTx]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #1567347778)
[INFO] [talledLocalContainer] -- referer: http://localhost:1990/confluence/plugins/servlet/upm | url: /confluence/rest/create-dialog/1.0/space-blueprint/dialog/web-items | traceId: 04182b73ba117a25 | userName: admin
Effects:
At this point you cannot create spaces again, even after restarting confluence. Disabling the plugin will cause the error while the plugin is disabled, but after re-enabling the error disappears. Uninstalling the plugin entirely will make the error (and thus inability to create spaces) permanent, until you perform the workaround below.
Workaround:
Once you have received the "unknown server error", you have to drop some tables and clear the plugin cache in order to be able to create a space again. I followed the instructions located here:
However, all this does is resolve the inability to create a space. Once you re-install the space blueprint plugin again and then disable or uninstall it (as happens frequently during testing!), you will once again be unable to create spaces until you perform the work-around again.
This error does not occur if I'm using Confluence 6.7.1, but occurs in 6.12.2 and 6.14.0. I've tested this both with the built-in database created when you perform an atlas-run on the plugin, and also in my development PostgreSQL 9.6 DB.
Essentially, what this means for me is that I cannot create a space blueprint plugin and deliver it to my client, because if they ever need to remove the plugin, it will "corrupt" the database (specifically the tables listed in the workaround).
Searching for issues related to the error I'm experiencing, I found the following:
https://community.atlassian.com/t5/Confluence-questions/Cannot-create-a-space-after-upgrade-to-6-12-0/qaq-p/930030
https://confluence.atlassian.com/confkb/unable-to-create-pages-the-create-page-popup-loads-forever-after-confluence-upgrade-to-5-x-330793034.html?_ga=2.45412717.813391250.1549382204-1439335163.1544544516
https://community.atlassian.com/t5/Confluence-questions/Cannot-create-a-space/qaq-p/903500
I have not found a method that prevents this error from occurring.
Are there any changes I need to make to the space blueprint to allow it to work in 6.12+? Is there something I've missed here? I wasn't able to find any bugs that looked specifically like this one, but I'm not the best at searching for existing bugs.
Hi @rashaveraka , I think if you check your application logs you'll find a NullPointerException like the one in https://jira.atlassian.com/browse/CONFSERVER-57943.
It occurs when a spaceblueprint entry is found without a wizard entry, which I believe happens when a spaceblueprint gets used and then disabled. I'm looking into the bug at the moment and hope to have more insight and a better workaround soon.
Hi Don, in my case no NPEs are present in the logs. Only output specified on line 22 is present.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Ross and welcome to the Community!
We have created a bug request from your notes. Thank you for providing extremely details notes on this issue as it helps when submitting a bug request. You may find your bug request at CONFSERVER-58001. You may watch this request to receive future updates of its status.
Once again, thank you for providing details steps into the issue you're experiencing with the Blueprint tutorial.
Regards,
Stephen Sifers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After a suggestion from a colleague, I turned on diagnostic logging and looked for a "Caused by" entry. None appears in the logs - just the error above occurs each time the "Unknown server error" dialog box popped up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.