Homepage | Products | OX Knowledge Base | Support | Try Now | Contact | Company
OX Logo
Results 1 to 4 of 4
  1. #1
    Join Date
    Jul 2008
    Location
    Hamburg, Germany
    Posts
    50

    Exclamation Funambol 7 GA + OX 6.6 RC5, Calendar Sync still not working

    Hi there,

    I was just curious if the latest Funambol with OX-Connector would now work with the latest Open-Xchange, so I fired up another test installation:

    Server:
    Debain etch (running 32 bit Kernel 2.6.24-19-xen as domU)
    Open-Xchange 6.6 RC5 (Build 6.6.0-6602, 2008-08-19)
    Funambol Bundle 7.0.6
    Funambol OX-Connector 7.0.3

    Client:
    Funambol PocketPC Plugin 7.0.8

    With Funambol 7, some configuration files moved, but the differences to 6.5 were not too difficult to handle.

    Unfortunately, calendar sync still doesn't work with latest OX (contacts and mail do work very well). Martin told me, this is due to API Changes within Open-Xchange.

    So it seems we'll have to wait for the ox-connector team to fix this...


    ds-server.log:
    Code:
    [2008-08-20 22:58:13,435] [funambol.engine.strategy] [INFO] [C654B791B32BA356364734D72A6E9099] [fwm-006030037193F5173] [testuser] [oxscal] Preparing slow synchronization
    [2008-08-20 22:58:13,439] [funambol.engine] [ERROR] [C654B791B32BA356364734D72A6E9099] [fwm-006030037193F5173] [testuser] [oxscal] Error preparing slow sync
    com.funambol.framework.engine.source.SyncSourceException: Error retrieving all item keys. 
            at com.funambol.ox.engine.source.OXCalendarSyncSource.getAllSyncItemKeys(OXCalendarSyncSource.java:359)
            at com.funambol.server.engine.Sync4jStrategy.prepareSlowSync(Sync4jStrategy.java:268)
            at com.funambol.server.engine.Sync4jEngine.sync(Sync4jEngine.java:652)
            at com.funambol.server.session.SyncSessionHandler.processModifications(SyncSessionHandler.java:1667)
            at com.funambol.server.session.SyncSessionHandler.processSyncMessage(SyncSessionHandler.java:1520)
            at com.funambol.server.session.SyncSessionHandler.processInitSyncMapMessage(SyncSessionHandler.java:961)
            at com.funambol.server.session.SyncSessionHandler.processMessage(SyncSessionHandler.java:517)
            at com.funambol.server.engine.SyncAdapter.processInputMessage(SyncAdapter.java:533)
            at com.funambol.server.engine.SyncAdapter.processXMLMessage(SyncAdapter.java:254)
            at com.funambol.transport.http.server.LocalSyncHolder.processXMLMessage(LocalSyncHolder.java:97)
            at com.funambol.transport.http.server.Sync4jServlet.doPost(Sync4jServlet.java:388)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
            at com.funambol.transport.http.server.LogContextFilter.doFilter(LogContextFilter.java:115)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
            at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
            at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
            at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
            at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
            at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
            at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
            at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
            at java.lang.Thread.run(Unknown Source)
    Caused by: com.funambol.ox.exception.EntityException: Error handling date in the get all method.
            at com.funambol.ox.items.manager.OXCalendarManager.getAllItems(OXCalendarManager.java:568)
            at com.funambol.ox.engine.source.OXCalendarSyncSource.getAllSyncItemKeys(OXCalendarSyncSource.java:354)
            ... 27 more
    Caused by: com.funambol.ox.exception.EntityException: Error while getting all items.
            at com.funambol.ox.items.manager.OXEntityManager.getAllItems(OXEntityManager.java:498)
            at com.funambol.ox.items.manager.OXCalendarManager.getAllItems(OXCalendarManager.java:566)
            ... 28 more
    Caused by: com.funambol.ox.exception.OXAccessException: JSONArray[4] is not a number.
            at com.funambol.ox.items.dao.OXEntityDAO.getAllItems(OXEntityDAO.java:1241)
            at com.funambol.ox.items.manager.OXEntityManager.getAllItems(OXEntityManager.java:494)
            ... 29 more
    Caused by: org.json.JSONException: JSONArray[4] is not a number.
            at org.json.JSONArray.getDouble(JSONArray.java:216)
            at org.json.JSONArray.getInt(JSONArray.java:233)
            at com.funambol.ox.items.dao.OXEntityDAO.getAllItems(OXEntityDAO.java:1160)
            ... 30 more
    [2008-08-20 22:58:13,476] [funambol.engine.strategy] [INFO] [C654B791B32BA356364734D72A6E9099] [fwm-006030037193F5173] [testuser] [oxstask] Preparing fast synchronization since 2008-08-20 22:53:03.453
    [2008-08-20 22:58:13,476] [funambol.engine.strategy] [INFO] [C654B791B32BA356364734D72A6E9099] [fwm-006030037193F5173] [testuser] [oxstask] Preparation completed.

  2. #2
    Join Date
    Feb 2007
    Location
    Germany
    Posts
    3,695

    Default

    Hi,

    that's true, we have escalated this issue to funambol and they are aware of the problem. It's up to them now to provide a solution as we pointed out this "change" of the API in numerous release notes and special reports to them. However, i am very sure they are eager to provide a fix soon as their software stack is also used for some commercial offerings in combination with Open-Xchange. We just released a final version of OX6 yesterday and customers are beginning their integration, until there is no fix for the funambol connector it will be a big problem for them.

    Some background information about this. It is not a real API change but a bugfix, we reviewed the behavior of the API and found out that we often use "0" for return values that are empty instead of NULL like it is documented at the API. Fixing this bug also fixes a lot of depending issues that are not obvious in daily operation but for 3rd party developers using our API. Our own clients like the ajax user interface or some testing frameworks also got some minor hickups after this fix - but it had to be done correct so we also fixed those follow-ups.

    Also hoping for a fast resolution from funambol
    Martin

  3. #3
    msmeyer Guest

    Default

    I see from the SVN logs on Funambol Forge that this problem has been fixed about two weeks ago, so there's hope that the next release of the OpenXchange connector will include a fix.

  4. #4
    msmeyer Guest

    Default

    Apparently, there's a new release, OX Connector 7.0.5 which includes the fix available for download here:

    http://forge.objectweb.org/project/s...hp?group_id=96

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •