Missing Call to AirVantage Session State Handler

Legato Application Framework
1

I posted this here in the Mangoh forum and I’m reposting here as this seems like a serious issue.

I have been working with @jchitty and @Prush on these questions Multiple Apps Calling le_avdata_RequestSession and Poor Signal Quality and Air Vantage Data Costs

Based on a discussion with @jchitty yesterday I have added AirVantage session state handlers to all (3) apps that request sessions. I have one test unit the I popped the antenna off and then back on after a few minutes (yes I know not recommended but I don’t have attunators at the moment) and this resulted in only 2 of the 3 handlers being called before the app is restarted. See logs below.

If you search for AV Session State Handler you will see two calls to the handler before the third app terminates due to a failed record push @ 22:32:10. Then you see three calls to the handler after app restarts and the system is trying to connect to AirVantage @ 22:34:15 and then another three calls to the handler once the system is again connected to AirVantage @ 22:37:38

The other interesting thing is I have a PushRecord callback handler that also doesn’t seem to be called as there are no log printouts.

Thoughts, why are all 3 apps receiving the state change.

Running Legato 18.09.0.

Missing Handler Call Log May 17th.log (51.3 KB)

Thanks

2

Hi @dbeckwith,
I am bit confused, Your question is “why are all 3 apps receiving the state change” or “why are all 3 apps NOT receiving the state change” when you remove the antenna and put it back ?

Please clarify.

Regards,
Muralidhara N.

3

@muralinagraj I was asking why all 3 apps were NOT receiving the state change notification.

4

Hi @dbeckwith,
From the logs provided there is no much information why the 3rd application(sensorToCloud) did not receive the the state change notification after you remove the antenna. But i think it looks a timing issue, By the time state change notification came, sensorToCloud app was terminated/restarted because it has been set to Assert if it fails to push the data.

Please verify again by removing the Assert condition when the sensorToCloud app fails to push the data OR provide the debug legato logs with the issue reproduced for us to analyze.

To enable the debug legato logs please run the command “log level DEBUG” on the console.

BTW, This scenario is 100% reproducible?

Regards,
Muralidhara N