Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
jeepee33
Partner - Contributor II
Partner - Contributor II

JSON RPC issue : received notifications on object handles after GetLayout(), GetFullPropertyTree()

After repeated calls to GetLayout() or GetFullPropertyTree() we receive notifications about changes in the objects.

Example of a response from Sense;

{"jsonrpc":"2.0","change":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95],"suspend":[1]}

Does anyone know why the Sense engine marks the objects as changed during 'read-only' actions ?

Thanks in advance

Labels (1)
2 Replies
Øystein_Kolsrud
Employee
Employee

That looks to me like a push notification from the engine. It's not your GetLayout or GetFullPropertyTree calls that triggers them (if it was, then the change notifications would come as part of the response for those calls). I would assume that something is changing the engine from another connection. Perhaps the app is being reloaded? Or perhaps you connected to an engine session that is already in use?

jeepee33
Partner - Contributor II
Partner - Contributor II
Author

Hi Yko,

Thanks for your response.

There are no other users and there are no reloads active.

However, our application performs an analysis on a large set of Sense apps. For each app in this set, a websocket connection  is set up.

To prevent a connection failure (because of a maximum of 4 sessions per user), we re-use the existing session cookie on each new connection.

Could this be the cause of our issue?