| Summary | Kolab backend: Crash on concurrent edit |
| Queue | Mnemo |
| Queue Version | Git master |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | thomas.jarosch (at) intra2net (dot) com |
| Created | 2012-11-07 (1749 days ago) |
| Due | |
| Updated | 2016-11-25 (270 days ago) |
| Assigned | 2016-01-18 (582 days ago) |
| Resolved | 2016-11-25 (270 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Sorry for taking so long to respond, I'm now actively working again on
the Kolab stuff.
State ⇒ Feedback
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ Kolab backend: Crash on concurrent edit
Queue ⇒ Mnemo
Milestone ⇒
Patch ⇒ No
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 172.16.1.253] 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:
https://172.16.1.123/horde/mnemo/memo.php?memo=mxstore%2800bf14a9-1ecc-4582-b1b9-613875b30bb0%29%3CeidFld%3A%3A%3C%28%29-0x0-0x0-0x0%3E%3CSE%3A0x200384%3E%3CRK%3A450f27bf2735e449bc4f0316970a60a1%3E%3E&memolist=ePGEQAhKP71Qjpi_cGDV7KA&actionID=modify_memo
Thomas