[Tickets #13022] Re: Exceptions to events break ActiveSync synchronization

noreply at bugs.horde.org noreply at bugs.horde.org
Tue Mar 25 21:03:56 UTC 2014


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13022
------------------------------------------------------------------------------
  Ticket             | 13022
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Exceptions to events break ActiveSync synchronization
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-03-25 21:03) wrote:

> Tried that, but now the client refuses to synchronize:
>
> [19:32:21] Exception| Stack trace follows...
> java.lang.ArrayIndexOutOfBoundsException: length=34; index=39
>         at com.android.exchange.adapter.Parser.push(Parser.java:422)
>         at com.android.exchange.adapter.Parser.getNext(Parser.java:506)
>         at com.android.exchange.adapter.Parser.nextTag(Parser.java:304)
>         at  
> com.android.exchange.adapter.FolderSyncParser.parse(FolderSyncParser.java:150)
>         at  
> com.android.exchange.EasAccountService.sync(EasAccountService.java:337)
>         at  
> com.android.exchange.EasAccountService.run(EasAccountService.java:165)
>         at java.lang.Thread.run(Thread.java:838)
>
> I have no idea what is going on, but a similar  
> ArrayIndexOutOfBoundsException is also logged in Bug #13052. Same  
> root cause?

No idea. I have no idea as to what can be causing that issue, if it's  
not due to the EAS version mismatch.

> Currently I can't explain why some (older) accounts synchronize  
> properly across all devices, but a new account created from scratch  
> won't.

The previous issues with the EAS version mismatch would explain this.

> I also don't understand where the timezone Africa/Ceuta is coming  
> from in the device log. I have configured PHP to use  
> Europe/Amsterdam and user preferences are also locked to this same  
> timezone. If I export to ICS, it correctly shows Europe/Amsterdam.  
> But what is logged on the device doesn't look anything like that  
> (see emaillog.txt.gz). I see weird things logged like
>
> [19:37:12] Calendar[arjen at de-korte.org]| All-day event arrived in:  
> Africa/Ceuta
> [19:37:12] Calendar[arjen at de-korte.org]| Not an all-day event  
> locally: Europe/Amsterdam
>
> Apparently, the device has the correct timezone (which is what I  
> configured in the Android settings), but events arrive with a  
> different timezone. Could it be there is something wrong with the  
> timezone settings in Kronolith?

No idea. The timezone blob sent to the device looks correct, so I  
doubt it's a problem with Kronolith or ActiveSync. Unfortunately,  
since I can't reproduce any of this, you are going to have to tackle  
this on your own.






More information about the bugs mailing list