|
[
Permlink
| « Hide
]
Melly Ismik added a comment - 19/Sep/07 04:25 AM
We have exactly the same problem. We are using IE 6 and running Confluence on a Windows server.
We have two clients with the same issue. The issue causes the latest edit to be lost, which makes it a critical issue and something that is undermining confidence in the system.
The problem went away when we stopped using the ajp proxy with apache
2.2 and used the http proxy instead. Brian We have always used the HTTP proxy which is the default as I understand. Still have the problem.
We have always used HTTP proxy (which is the default as I understand
it). Still have the problem. Melly Ismik Related issue
We haven't seen it happenning with page move. But that is not a feature used as frequently as page edit.
/Melly Hi,
I'm having some trouble replicating this error and will need some more information. It would be great if you could use Wireshark Agnes. We will try and install Wireshark to help collect some info. In the meantime, I will attach the logs we managed to save around the time this issue has happened.
Here are the comments from the user: !! I was asked to enter a page title as experienced by Joe and all my edits were gone! When I now try to edit that page it recognises that I was editing it previously: A version of this page you were editing at Sep 13, 2007 10:39 was not saved. Do you want to resume editing or discard it? but when I try to resume editing, I get another error message: The page you were trying to reach does not exist. You may want to try a search, or browse the site to find the page you were looking for. Attaching logs collected at the time of the error
We're no longer seeing it as we've got to an http proxy instead of an
ajp proxy. The ajp proxy was truncating the data coming back from tomcat, so its possible that javascript chunks were dropped causing this problem. I continue to see this error (I have not upgraded to 2.6 yet to see if that resolves the issue). The error does not occur unless the "move children" checkbox is selected. Until I saw this issue it never dawned on me that it could be a Safari only related issue. I will try the same page moves today in FireFox and see if that resolves the issue. I will also give WireShark a try.
The error is difficult to replicate as it is intermittent and rare on our instance of Confluence. However, we are keeping an open mind that the error occurs with different frequency in different instances of Confluence.
One client has suspended their roll-out of Confluence until this has been resolved. Glad to see that somebody managed to capture an occurrence in the logs. Did this shed any light on the error? I got the same problem
Confluence Version: 2.5.6 Build:#812 Aug 06, 2007 Thanks for the additional information. This will help our investigation.
Hi Melly,
Can you please try disabling the scaffolding plugin to see if this removes the problem? Agnes. Note: I used Scaffolding 2.3-dr7 for my testing
We are not getting this error in relation to moving the pages but I have disabled the scaffolding plug-in anyway in case it makes a difference. We had version 2.3-dr6.
Good to hear! (Tom)
So did that fix your problem Melly? Agnes. I cannot say the problem has gone away as we are not able to re-produce it at will. But we haven't experienced it for a while now.
Has anybody been able to estimate the frequency with which this problem occurs?
Lars,
Atlassian did provide a suggested resolution in the ticket which we are currently testing. Can you provide an estimate of when you will provide the other bug-fixes - we have been waiting a few weeks now for the bullet point and recently updated fixes Trish Trish, please comment on the relevant issue with your question. I'm not sure which ones you're referring to.
The error is back! The only change in our environment was that we turned on the 'access logging'. Could this be related? I will attach the logs.
The error occourred at 18:39 the first time when changing a label on a page. Then again 10 minutes later when removing a label. Previously we had to put our Confluence roll-out plans on hold because of this issue. Re-occurrance represents a serious set-back for our plans. I hope we can find a solution to this. Logs collected around the time of the 'Enter a page title' error. We had the 'access logging' turned on.
Melly,
Please raise a support case at https://support.atlassian.com Agnes was able to confirm that this particular problem was caused by the Scaffolding Plugin, so I'll be raising an issue with the maintainers and closing this issue shortly. Your situation may be some other kind of problem, which our support engineers will be able to determine. Thanks for your help. Regards, Hi all,
I believe this is the same issue as described here: http://jira.adaptavist.com/browse/SCAFF-158 It was resolved in Scaffolding 2.6-dr8, but will require Confluence 2.6 to run. If there are any other issues you come across with that combination of plugin/Confluence please raise a new issue with the details. Thanks, David This can be fixed by upgrading the Scaffolding Plugin. Please see the issue in the plugin's issue tracker:
This problem has gone away after we disabled the Scaffolding Plugin. It remains disabled. However the issue has appeared again.
I'm having this same issue, but can't see the resolution details. Could I be added to the "watch" list or something to see the steps involved solving it?
sorry about that.. my mistake. I was viewing the wrong tab - please ignore.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||