|
Ok David,
Confluence log attached: atlassian-confluence.zip Resgards, Ok, it looks like the root cause is a StackOverflowError. The usual cause is that there is some recursive markup somewhere in the system. My guess would be that somewhere in a {text-data} field is some wiki markup which ends up re-executing the current page, which loops through again, and again, and again, until the system runs out of memory. Is there any markup like that around on the page you're having problems with?
Dear David,
We tested each line of code template that we try to save and identify row below that is generating the error. Any ideas?
Best regards, The problem is probably what is stored in the field, not the field itself. Although, having a ':' in a field name is very unusual. I don't think it would cause problems, but it's possible I guess...
What is the current value of the 'Descrição:' field? Well, this field has no value because it is a template. We are trying to save a template. (Browse Space> Edit Template) Excluding the ":" of the field, the error still exists but in another format (see attached file: ErroScaff-232.jpg ) Very odd. I've assigned it to the next version so that we will investigate it before the next release. Unfortunately, it won't be immediately - we have some other projects that need to clear the pipeline first. I'll keep you posted here. In the meantime, perhaps you could use {text-data} until the issue is resolved.
Hi Roberto,
Sorry, we ran out of time to investigate this issue for 3.0.0. I've assigned it to be examined in the next release. David Hi there. I'm unable to replicate this issue in 3.0.0 or 3.0.1. Could you please confirm, and if there are still problems, re-open this issue.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
Other than the choice of database server, the rest looks pretty standard. There are some configuration requirements
for SQL Server, but I'll assume for the moment that those have been followed.
That being the case, I will need the full stack trace from the web server logs to be of more assistance. Unfortunately, the 'UnexpectedRollbackException' is about as helpful as a 'General Protection Fault' in Windows, but it's all that gets displayed to the user if there's an error. To get the full log, you may have to turn on logging and restart Confluence, then replicate the error.
To turn on logging, do this:
1. Find "<your confluence server>/confluence/WEB-INF/classes/log4j.properties"
2. Edit the file, and look for the lines relating to 'atlassian-confluence.log'
3. Remove the '#' markers in front of them if they are present.
4. Save, and restart Confluence.
Let us know what you find.