Client stops after 6:25 hours...

RE: Client stops after 6:25 hours...

tesc — Thu, 11 Feb 2021 10:22:13 GMT

Hi,

Thank you for the update. You can of course use the time that you need. Feel free to continue the discussion if you find anything in your debugging, or have new related questions.

Regards,
Terje

RE: Client stops after 6:25 hours...

JVKran — Wed, 10 Feb 2021 14:32:42 GMT

Hi Tesc,

Sorry for the delay. Thanks for letting this know. I made a reasoning mistake regarding the tid's. The application doesn't do anything with the tid's. I assumed they were neccesary for the model to operate.

Okay, so, I've got some debugging to do ;). Thanks anyway!

Kind regards,

Jochem

RE: Client stops after 6:25 hours...

tesc — Thu, 28 Jan 2021 15:17:42 GMT

Hi,

Setting the field manually to 0 when it is about to overflow should have the same effect of letting it overflow, so both working the same is as expected.

I have not found anything in the simple on/off model that indicates that an overflowing tid field there should cause any issues. I did not find any check of that field on the server side, similar to the model_tid_validate() function used by the generic on/off model and others. The field is on the application level, and so the implementation for checking it is up to the application. I would start by checking how the application handles the field, in both ends.

Regards,
Terje