Results 1 to 5 of 5
  1. #1
    Member
    Join Date
    Jan 2008
    Location
    Paris
    Posts
    3

    Error: Token not found while parsing a GIS reques

    Hello,
    We are migrating from version 3.4.6 to 3.5 of Lightstreamer and we have un exception in LS:

    Caught exception: Token not found while parsing a GIS request
    Lightstreamer.DotNet.Server.RemotingException: Token not found while parsing a GIS request
    at Lightstreamer.DotNet.Server.MetadataProviderProtoc ol.ReadGetItems(String request) in c:\LIGHTSTREAMER\PROJECT_Lightstreamer_3_Remote_Ad apter_1\DotNetAdapter\Source\MetadataProviderProto col.cs:line 379
    at Lightstreamer.DotNet.Server.MetadataProviderServer Impl.OnRequestReceived(String requestId, String request) in c:\LIGHTSTREAMER\PROJECT_Lightstreamer_3_Remote_Ad apter_1\DotNetAdapter\Source\MetadataProviderServe r.cs:line 206

    Do you can help us?

    Regards,
    Andrei.

  2. #2
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    975
    The 3.5 version of the Server extended the "adapter remoting infrastructure" protocol, breaking the compatibility with older Remote Adapters.
    In fact, Remote Adapters should be extended and recompiled according to the 1.5 .NET Adapter SDK version.

    However, a workaround for ensuring backward compatibility was provided:
    you can stick to the old version of the Proxy Adapter,
    that is, you can keep the version of ls-proxy-adapters.jar provided by the 1.1 Adapter Remoting Infrastructure SDK (which corresponds to Server 3.4.6).

    The extended 3.5 Server supports the old 1.1 ls-proxy-adapters.jar, which, in turn, communicates with Remote Adapters based on the 1.3 .NET Adapter SDK version.
    The changelog provides details on the extension.

  3. #3
    Member
    Join Date
    Jan 2008
    Location
    Paris
    Posts
    3
    Thanks for the reply
    We changed the ls-proxy-adapters.jar and files with version of JS API.
    Now Ls works fine.

    A small question: Are important to change the files containing the version of API Javascript (build.number, compatibility_version.number and version.number)?
    Do you use they in initialization of javascript library?

    Thanks a lot for your support.

  4. #4
    Power Member
    Join Date
    Jul 2006
    Location
    Cesano Maderno, Italy
    Posts
    784
    A small question: Are important to change the files containing the version of API Javascript (build.number, compatibility_version.number and version.number)?
    Do you use they in initialization of javascript library?
    those files are not used at all by the library, btw, when someone reports an issue, the first thing we ask for is the build number of the library, so it's better if you keep 'em aligned with the library

  5. #5
    Member
    Join Date
    Jan 2008
    Location
    Paris
    Posts
    3
    Ok,
    Thanks for your response.

 

 

Similar Threads

  1. Replies: 1
    Last Post: January 31st, 2011, 08:47 AM
  2. Replies: 2
    Last Post: March 19th, 2008, 11:19 AM
  3. Replies: 2
    Last Post: November 6th, 2007, 05:13 AM

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
  •  
All times are GMT +1. The time now is 07:40 PM.