[#11668] Kolab backend: Crash on concurrent edit
Summary Kolab backend: Crash on concurrent edit
Queue Mnemo
Queue Version Git master
Type Bug
State No Feedback
Priority 1. Low
Requester thomas.jarosch (at) intra2net (dot) com
Created 2012-11-07 (1358 days ago)
Updated 2016-03-08 (141 days ago)
Assigned 2016-01-18 (191 days ago)
Resolved 2016-03-08 (141 days ago)
Patch No

2016-03-08 10:57:44 Jan Schneider State ⇒ No Feedback
2016-01-18 20:04:37 Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
Is this still an issue?
2012-11-07 17:01:13 Thomas Jarosch Comment #1
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Mnemo
Summary ⇒ Kolab backend: Crash on concurrent edit
Type ⇒ Bug
Priority ⇒ 1. Low
Reply to this comment

lets assume we successfully synced in some notes from the server.
These notes reside in a shared folder.

One client edits a note, the other client didn't update the IMAP cache yet.

If I now try to edit the note on the not-updated-yet client, I'll get a crash:

[Wed Nov 07 17:58:05 2012] [error] [client] PHP Fatal 
error:  Call to a member function getFullMsg() on a non-object in 
/datastore/DEVEL/horde/framework/Kolab_Storage/lib/Horde/Kolab/Storage/Driver/Imap.php on line 419, referer: