Hi Brad, just to be bring some light, try to bring the cached values (via memcache_fetch() ) in separate values and print them on the spot (after the fetch). This will clarify if it is an issue with memcache code or if it an error in handling the variables.
Regards, Bogdan Brad Bendy wrote: > Hi List, > > I ran into something interesting today (have not noticed this in the > past anyways). > > We set a extra variable in the acc table for the gatewayId, we pull > these values from a memcache store, with some recent changes in our > code we now sometimes hit memcache twice for a gatewayId the second > time is always a different value (both are executed before we run we > call t_on_reply(), etc. > > Now it is storing the 1st value and not the 2nd value in the acc table > it looks like as soon as the value is assigned that is the value that > is then stored in the acc table, has anyone else seen this and is this > the correct behavior? If so anyway to change it so the last value of > the avp is what is stored? When the avp value changes it's from the > memcache_fetch() call. > > This on 1.6.2 I have not tried on other releases yet but will later on > tonight, we have done this same type of thing in the past and it has > appeared to work, but I will have to verify to make sure. > > Thanks > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Bogdan-Andrei Iancu www.voice-system.ro _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users