Xibo

Pyclient DataSet NOW() filter cache issue?

Asked by Sven Persson

I've set up a dataSet with following guide: http://xibo.org.uk/2014/05/27/using-datasets-to-display-meeting-room-bookings/

The issue is that the pyclient does now update the filter settings according to DataSet date/time (“NOW() > dtMeetingStart AND NOW() < dtMeetingFinish”) in the region (i'm using TICKER function to show the dataSet)

It seems that the data is cached somewhere in the pyclient even if I've adjusted the cachetime both in site.cfg and the TickerRegion settings.
You can see this issue if the dtMeetingFinish has passed and the dataset data is still showing on the screen.

I'am using the latest version of CMS 1.6.3 and pyclient (1.6.0 RC2)
.net client is working fine.

Is this a bug or should I adjust something more?

Thank you.

Question information

Language:
English Edit question
Status:
Answered
For:
Xibo Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Alex Harrington (alexharrington) said : 		#1

Updated data won't be shown until the client has had time to connect to the
CMS after dtMeetingFinish (when the dataset would return the new data) and
then the layout showing that data is restarted.

So for example, if you show a layout that has that dataset ticker on it
with a duration of 3600 seconds, then in the worst case it would be a full
hour after the meeting finished before the updated data was shown.

What you need to do is keep your ticker duration short so the layout
refreshes frequently and shows the most up to date data, and ensure that
the data set refresh time is kept low or even 0 so that a fresh copy is
pulled each time the dataset ticker is shown.

Revision history for this message
Sven Persson (3-info-l) said : 		#2

Thats what I've been trying. I adjusted the ticker duration to 60 seconds and then I played around with the dataSet data and publishing times to see the live changes in action.

I have 2 clients connected to the layout, one pyclient and one .net client.
the .net clients is working perfect and the pyclient does not.

I adjusted the pyclient loglevel to 3 and to screen, but I cannot see something odd in there.

any other suggestions?

Revision history for this message
Alex Harrington (alexharrington) said : 		#3

Was the cache time set high initially?

If it was, the client will still be caching it. You can safely delete the
contents of the client local library to check

Revision history for this message
Sven Persson (3-info-l) said : 		#4

I guess the standard value. I purged the datafolder also yesterday and now I did it again.
I can confirm that it's working better after data purge but again a while after this the same issues still there.
It's like the cache flush not working.

Can someone else confirm that this have been working fine in 1.6.3 and pyclient?

Revision history for this message
Sven Persson (3-info-l) said : 		#5

I've now tried multiple types of hardware and also ubuntu 10.04 with the old pyclient.
I really believe that this issue is an bug in the pytonclient!

Revision history for this message
Dan Garner (dangarner) said : 		#6

Ive marked up the bug so we take a look for 1.6.4.

Can you help with this problem?

Provide an answer of your own, or ask Sven Persson for more information if necessary.

To post a message you must log in.