Error loop on client sleep wake

[admin]

Freeze in normal as the system tries to re-establish network connection during that time.
Would really appreciate a small video clip (you can use your phone, for instance to record what happens on the PC screen, so no need to install anything...) Thanks!

[Trinitylab]

Admin, can't agree, as for a couple of years EPIM on the host did not freeze, ie. one could easily use DB after PC went idle, and then awoke. No message or anything. This is how it worked.

[admin]

And this is how it supposed to work now with the 8.6 version. That's why I'm so persistent in asking you for a short video, so that we could see how this is working on your side.
Also, please let us know (if you happen to remember that), which of the previous versions you remember worked as expected for you?

[Trinitylab]

Definitely 5.x, later not sure.

[admin]

It might seem so as there were much less requests to the networked database file in the 5.x versions of EPIM simply because the program itself was less advanced at that time. But if you, for instance tried to switch from one module to another with the 5.x series version you'd face the same freezing situation.

[TumbleDoor]

So the thing I don't get here is why don't you just add a connection re-try button to the error message?

It seems like the issue here is that EPIM only tries to reconnected to the database on it's own terms which is way to fast and aggressive for the average time it takes for the NIC to come back online after sleep or the average bump in the network. So by having a re-try button the user can hit they can just wait for the network to come up and then hit the button.

[admin]

It should be trying to connect each time you click on the Ok button. But so far we weren't able to test that out as we couldn't make that message to come up. So; it still points in the short demonstration video direction..

[MetalDrop]

Well I can provide a video of what hitting the OK button currently dose [RC2] after a temp network lose which is close out of EPIM. There is no attempt to reconnect just instant terminate.

[admin]

Yes, this is by design.

[TumbleDoor]

Well that seems like rather conflicting messages.

First you say, "It should be trying to connect each time you click on the OK button. "

Then you say that by design clicking OK terminates the program.

[admin]

This is a different message that you can see in the video.

[TumbleDoor]

This is a different message that you can see in the video.

I wasn't talking about the freeze message, don't know anything about that haven't ever experienced it myself.

I wanted know why when there's a temporary lack of internet why EPIM can't be made to try re-connecting, rather then just killing itself.

It's nice not to have to manually kill it in the task manager anymore, but it's still an annoying/bad solution.

It would be like Chrome, IE, of Firefox killing itself because you lost internet or your computer went to sleep well working in google docs.

[admin]

See here, last sentence: viewtopic.php?p=108002#p108002.

[MetalDrop]

Slept the computer and came back 8hrs later and the error loop started back.

It seems to happen when EPIM is minimized and the system is slept for a long period of time.

If EPIM is left OPEN when the computer goes to sleep it won't go into the loop. It seems to have to be minimized and it seems to have to be for a number of hours.

I'll turn on logging and test this again tonight when I go to bed I'll leave EPIM connected and minimized.

[MetalDrop]

One restful night later it seems to be confirmed:

Video and log files attached

Recap:
If EPIM is minimized and the computer sleeps for a number of hours it will still go into an infinite loop.