Re: [tauruslib-devel] Tango server and Taurus client interaction problem.

[Александр С. <sen...@gm...>]

Hello Zbigniew,

I have run both of tests, no memory usage growth was observed.
It seems that avoiding "signal.name" is acceptable solution.

Thanks for your help!



2015-08-04 16:00 GMT+06:00 Zbigniew Reszela <zre...@ce...>:

> Dear Alexander,
>
> To be honest I've not experienced this problem before. But I will try to
> help you with what I know.
> The warning message comes from the push_event method of the
> TangoConfiguration class.
> This method is passed as a callback when subscribing to the attribute's
> configuration event.
> In the code it has an interesting comment:
>
> #===================================================================
> # This is a safety net to catch "zombie" TangoConfiguration objects
> # when they get called.
> # If you get here, there is some bug elsewhere which should be
> # investigated.
> # Without this safety net, you would get exceptions.
> # We assume that a TangoConfiguration object which has no listeners
> # and which is not associated to a TangoAttribute, is a "zombie".
>
> From the taurus script which you attached in the Tango forum entry, the
> code responsible for subscribing to this event is: signal.name.
> The attribute name is obtained from the Tango configuration object and
> Taurus subscribes to configuration events the first time one tries to
> obtain some value from it like label, units, name, etc..
>
> In order to debug the problem could you please:
>
> 1) Try to do not use the signal.name in your code and substitite if by
> signal.getSimpleName() and check if the memory also grows?
>
> 2) Try to execute the following code and see if the memory also grows:
>
> import time
> import PyTango
>
> period = YOUR_POLLING_PERIOD
> d = PyTango.DeviceProxy(YOUR_DEVICE_NAME)
>
> while True:
>     print d.read_attribute('signal').value[0:5]
>     time.sleep(period)
>
> Please let us know about results of your tests.
>
> Cheers,
> Zibi
>
>
>
> On 08/03/2015 09:05 AM, Александр Сенченко wrote:
>
> Hello.
>
> I have been faced with a problem.
> When i connect to tango server from taurus client, server memory usage
> grows.
> When i use C++ client or jive, it doesn't.
>
> When server increases memory consumption, taurus client issues a warning:
> Dummy-2 WARNING 2015-07-30 18:24:55,560
> devhost:10000.simple2/gen/dev1.signal.configuration:
> "Zombie" object
> (TangoConfiguration(devhost:10000/simple2/gen/dev1/signal?configuration))
> received an event. Unsubscribing it.
>
> Tango Server system:
> CPU powerpc
> OS debian lenny
> gcc 4.3.2
> Tango 8.1.2c
> zeromq 4.1.2
> omniorb 4.1.6
>
> Taurus Clietns system:
> CPU intel I7
> OS debian 8 jessie amd 64
> gcc 4.9
> omniorb 4.1.6
> zeromq 4.0.5
> tango 8.1.2c
> taurus 3.3.1
>
>
> I also started discussion in Tango forum:
> http://www.tango-controls.org/community/forums/topic/99/
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Tauruslib-devel mailing lis...@li...://lists.sourceforge.net/lists/listinfo/tauruslib-devel
>
>
> --
>
> --
>
>
> [image: ALBA Synchrotron] <http://www.albasynchrotron.es>
> Zbigniew Reszela
> Controls Section - Computing Division
>
> ALBA SYNCHROTRON LIGHT SOURCE Ctra. BP 1413 km. 3,3 | 08290 | Cerdanyola
> del Vallès| Barcelona | Spain
> <http://www.albasynchrotron.es/AboutUs/Access>
> (+34) 93 592 4407 www.albasynchrotron.es | zre...@ce...
>
> *Please, do not print this e-mail unless it is absolutely necessary. *Si
> heu rebut aquest correu per error, us informo que pot contenir informació
> confidencial i privada i que està prohibit el seu ús. Us agrairíem que ho
> comuniqueu al remitent i l'elimineu. Gràcies.
> Si ha recibido este correo por error, le informo de que puede contener
> información confidencial y privada y que está prohibido su uso. Le
> agradeceré que lo comunique a su remitente y lo elimine. Gracias.
> If you have received this e-mail in error, please note that it may contain
> confidential and private information, therefore, the use of this
> information is strictly forbidden. Please inform the sender of the error
> and delete the information received. Thank you.
>