Forums/ScreenSteps Desktop/Workgroup/ScreenSteps Desktop
Answered
Problem exporting to Confluence 3.1
william.s.hayes
asked this on March 18, 2010 22:38
When trying to upload to one specific space, I'm getting the following error:
"A problem occurred while uploading the lesson:
server error (java.lang.Exception: org.springframework.transaction.UnexpectedR Transaction rolled back because it has been marked as rollback-only)"
I can export to other spaces on the wiki. Any ideas? I didn't see any errors in the Confluence logs/Catalina.out
Thanks!
Comments
Off the top of my head I'm not sure why Confluence would generate that error. This happens with any lesson you try to upload to the space? If so then have you looked to see if there are any permission differences between the misbehaving space and spaces that work?
It happens with any lesson I tried to upload to that space. There isn't a permission difference for that space compared to the others, and until yesterday we had no problem uploading to the space using ScreenSteps. It is the largest wiki space on our Confluence server, but I don't know why that would affect anything. If you don't have any troubleshooting ideas, I'll try over with the Atlassian support to see if they can figure out any ideas for troubleshooting. We set up another space that we are exporting into so this isn't stopping work - just worried that it's a harbinger of something else.
Being able to export Screensteps directly to the wiki has been fantastically useful. In fact, I've been telling everyone I can about Screensteps because it is AWESOME. I now enjoy doing tutorials and pop them out in minutes - several times faster than before.
Unfortunately I don't know where to start looking for this error as I'm not familiar with how Confluence works under the hood. If you find out any new information from Atlassian let me know.
I'm glad to see that ScreenSteps brought a little more joy into your life :-)
Hi Trevor,
I have got the exact issue in our system also and the error description matches same with that if william.
Hope you guys are also investigating the issue.
Hi Gaurab,
This is not an issue that we are investigating as we haven't ever seen it on our end. Since Confluence is experiencing an internal error and doesn't provide any information about what the error is we don't have much to go on.
If someone can provide a recipe or provide access to a testing environment where the error occurs then I can look into it.
I was able to reproduce this error using Screensteps 2.9.1 build 30 and our instance of Confluence (4.1).
I do get this error message whenever I try to export a lesson to Confluence that was already exported (ie the Confluence page already exist).
I if delete the Confluence page then export the lesson, it works just fine.
Having to remove an existing Confluence page in order to export an updated lesson has some drawbacks:
Trevor, can you please try to re-produce the problem and advise?
Thanks!
Raf
Raf - I will look into this at the beginning of next week and get back to you with what I find.
Raf - I found the root of the problem that you are encountering. In Confluence 4.0 a change was made to the API that disallows retrieving page contents using the version 1 API. ScreenSteps tries to fetch a page from Confluence to determine if a lesson should be created or updated on the server. Since the version 1 API would fail every time ScreenSteps was trying to create a new page. I don't think Confluence likes having two pages with the same name which elicits the error message that is being returned.
I've created a new build of ScreenSteps for you to try. This build fixes the issue in my tests with Confluence 4.1. Let me know if this works on your end. Thanks for the detective work.
OS X: http://www.bluemangolearning.com/download/screensteps/2_0/test/ScreenSteps%202.9.2r17.dmg
Windows: http://www.bluemangolearning.com/download/screensteps/2_0/test/ScreenSteps%202.9.2r17.exe
That is excellent Trevor! I can know upload an updated lesson to Confluence 4.1. Thanks for the fix!
On a side note, how does Screensteps handle the Confluence page history?
If I change a screenshot in Screensteps and export the lesson to Confluence, the page history will show the latest screenshot for all the page version.
Is there a way for Screensteps to take advantage of the page history feature of Confluence?
Imagine being able to easily modify a lesson AND see what the changes were.
Food for thought. With the fix you've released we can now start using Screensteps!