Hi,
Are you sure item 188 is still subscribed to by at least one client when you inject the update from the Adapter?
Cheers,
Alessandro
Hi,
Are you sure item 188 is still subscribed to by at least one client when you inject the update from the Adapter?
Cheers,
Alessandro
I'm pretty sure it's still subscribed - the Unsubscribe method is not being called before I call Update.
Also, from the .Net side I see the following in the log. I don't know if it helps.
33775 [1496] DEBUG Lightstreamer.DotNet.Server.RequestReply.NotifySen der (null) - Notify line: 1248872819081|UD3|S|188|S
|100000122c6d583bd|B|0|S|value1|S|1|S|value2|S|cra ig
hi,
depending on the client version in use that string could represent an update for a table that has two fields, one valued as 1 and the other valued as null, OR, a table with a single field which value is null. Which is the build number of the web client you're using?
this is your update as it flows from the remote adapter to the server as described by the ARI protocol. Nothing strange here.Code:1248872819081|UD3|S|188|S |100000122c6d583bd|B|0|S|value1|S|1|S|value2|S|craig
Is it possible that your client is subscribing to the correct item but with the wrong schema?
Is the WARN message on the server continuously logged?
Can you check the communication between client and server?
If is it possible please attach here a server log snippet that shows the issue.
Yes, the problem was that I had incorrectly implemented my overrides of the GetItems and GetSchema methods of the MetadataProviderAdaptor. I have it working, though I now have a different problem that I will start a new thread for.
Bookmarks