Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 336025

Summary: Task synchronization issues with Bugzilla and mod_perl
Product: z_Archived Reporter: Kenn Hussey <Kenn.Hussey>
Component: MylynAssignee: Project Inbox <mylyn-triaged>
Status: CLOSED MOVED QA Contact: Frank Becker <eclipse>
Severity: normal    
Priority: P3 CC: robert.elves, steffen.pingel
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description Kenn Hussey CLA 2011-02-01 18:34:40 EST
We recently moved our Bugzilla installation from a local server to an Amazon EC2 instance. Ever since, task synchronization (even for a brand new task list in a new workspace) hasn't worked correctly; outgoing changes are successfully submitted, but for some reason aren't marked as such, and the task list then thinks that incoming changes conflict with unsubmitted local changes (which have already been sent).

I am using the latest Mylyn from Helios with Bugzilla 3.0.6 (I know, that's old, but we were using the same version successfully on our previous server)...
Comment 1 Steffen Pingel CLA 2011-02-01 18:36:25 EST
Is there anything in the error log indicating a failed submit? Does the task editor show an error in the header?
Comment 2 Kenn Hussey CLA 2011-02-01 19:31:14 EST
(In reply to comment #1)
> Is there anything in the error log indicating a failed submit? Does the task
> editor show an error in the header?

Nope, nothing in the error log. I see a "Changes submitted" message at the top of the task editor, but the task list still shows outgoing changes (the gray arrow). When I refresh my task list, I see a conflict on the task (a red double arrow). When I reopen the task, I see that my changes have been made (e.g., the comment has been added) but I also see that I still have pending changes (e.g., there is text in the new comment field).

New tasks that I create remain in the 'Unsubmitted' category forever (but incoming copies from the server have keys assigned and all the right attrtibute values.
Comment 3 Steffen Pingel CLA 2011-02-01 19:40:06 EST
Frank, do you have any ideas why the outgoing state is not properly cleared?
Comment 4 Kenn Hussey CLA 2011-02-02 12:11:41 EST
We took a closer look at the configuration of our Bugzilla and it turns out the problem seems to have been with mod_perl (http://www.bugzilla.org/docs/tip/en/html/configuration.html#http-apache-mod_perl). Once we switched back to CGI mode, the problem went away. In case others might run into similar problems, it might be worth updating the FAQ/documentation for the Bugzilla connector with this information.
Comment 5 Steffen Pingel CLA 2011-02-02 13:52:08 EST
That's good to know. We should figure out if that is a general problem or if there are specific configuration options that need to be in place. mod_perl usually makes Bugzilla a magnitude faster and Eclipse.org uses it as well which seems to work with Mylyn.
Comment 6 Kenn Hussey CLA 2011-02-02 14:29:14 EST
(In reply to comment #5)
> That's good to know. We should figure out if that is a general problem or if
> there are specific configuration options that need to be in place. mod_perl
> usually makes Bugzilla a magnitude faster and Eclipse.org uses it as well which
> seems to work with Mylyn.

Hmm. It's odd that it works for Eclipse. Our best guess was that it somehow resulted in timestamp anomalies. Maybe it had something to do with our configuration... here's what we had:

#
# Bugzilla mod_perl configuration
#
#
PerlOptions +Parent
PerlSwitches -Mlib=/var/www/bugzilla -w -T

PerlConfigRequire /var/www/bugzilla/mod_perl.pl

Alias /bugzilla/ "/var/www/bugzilla/"
Alias /bugzilla "/var/www/bugzilla"

We're installing a newer version of Bugzilla and we'll try mod_perl with that to see if there's any difference...
Comment 7 Kenn Hussey CLA 2011-02-03 09:22:51 EST
(In reply to comment #6)
> We're installing a newer version of Bugzilla and we'll try mod_perl with that
> to see if there's any difference...

The same problem occurs for us on Bugzilla 3.6.4 with mod_perl configured. :(

Maybe I'll ask Webmaster to see how Eclipse has configured their server...
Comment 8 Kenn Hussey CLA 2011-02-03 09:57:08 EST
(In reply to comment #7)
> The same problem occurs for us on Bugzilla 3.6.4 with mod_perl configured. :(

We have been able to avoid the issue by disabling keep-alives:

# Disable keep-alives
KeepAlive Off
Comment 9 Steffen Pingel CLA 2011-02-03 16:56:14 EST
(In reply to comment #8)
> We have been able to avoid the issue by disabling keep-alives:
> 
> # Disable keep-alives
> KeepAlive Off

Thanks for following up on that. It doesn't sound good that this setting would cause the described problem. We'll try to reproduce this.
Comment 10 Frank Becker CLA 2011-02-04 01:07:53 EST
(In reply to comment #9)
> (In reply to comment #8)
> > We have been able to avoid the issue by disabling keep-alives:
> > 
> > # Disable keep-alives
> > KeepAlive Off
> 
> Thanks for following up on that. It doesn't sound good that this setting would
> cause the described problem. We'll try to reproduce this.

Steffen, shoud i try to change my local Installation for this?
Or do you have One?
Comment 11 Steffen Pingel CLA 2011-02-04 01:28:26 EST
That would be great. I don't have a test setup with mod_perl at the moment.
Comment 12 Eclipse Webmaster CLA 2022-11-15 11:45:08 EST
Mylyn has been restructured, and our issue tracking has moved to GitHub [1].

We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub.

[1] https://github.com/orgs/eclipse-mylyn