-
February 2nd, 2010, 06:07 PM
#1
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.
-
February 3rd, 2010, 09:16 AM
#2
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.
-
February 3rd, 2010, 11:03 AM
#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.
-
February 4th, 2010, 09:30 AM
#4
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
-
February 5th, 2010, 03:12 PM
#5
Ok,
Thanks for your response.
Similar Threads
-
By msgiribabu in forum Adapter SDKs
Replies: 1
Last Post: January 31st, 2011, 07:47 AM
-
By tuongkha in forum Adapter SDKs
Replies: 2
Last Post: March 19th, 2008, 10:19 AM
-
By tuongkha in forum Adapter SDKs
Replies: 2
Last Post: November 6th, 2007, 04:13 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 10:47 AM.
Bookmarks