Reconnect to ModelManager Automatically

[PeterKehoe]

If the LAN connection is broken and then reconnected while ModelManager is running, automatically reconnect the ModelManager client to the database when the LAN connection is reestablished.

[ptc-1796640]

I've been suffering with this for a long time on WorkManager v.12, but have consoled myself thinking it would be fixed once I moved to ModelManager. I'm disappointed to hear this hasn't been addressed yet.

It affects me when I undock my laptop (switching from ethernet to wifi), and when working from home via VPN which has a greater likelihood of briefly losing a connection.

[MaxKublin]

In Workmanager, it was quite easy to re-connect without restarting the application.

We even had customers switching from one DB to another to perform administrative tasks.

Basically you could do:

INPUT 'startup"

But there are other ways to to just the re-connect.

All done by Macros, so you can re-connect just from the WM command line.

You only need to know the (few) Commands/Functions to call.

This was possible in WM since WM does not have all these preferences, tags etc. that MM has.

Also, the type of connection between WM and CAD is not as tight as it is between MM and CAD.

[JamesOsborn]

I wouldn't mind if it required to re-enter credentials if that is deemed required.  It just seems silly to pop up the error and force the user to un-check/re-check the module to get over this.  I suppose for environments with flakey networks, having to re-authenticate would be undesirable...

[MaxR.Kublin]

Re-entering the credentials is the smallest part of Model Manager's issue.

The real issue is that MM loads/initializes (=caches) many data structures when it starts up,

and unfortunately, the code is not able (designed?) to re-initialize itself.

The only way to initialize MM currently is to start it from scratch.

[MaxR.Kublin]

In environments with "flakey Networks", losing the connection to the Database is a "small evil" - compared to potential data corruption in the database.

If the connection to the database is lost, the problem is much bigger than just re-connecting Model Manager.

Btw. "the disconnect" only applies to the database connection.

The connection to the file server is made "on demand" - when a file is loaded or stored to the File Server (storage area).

The same is true for the connection to the license server.