Skip to main content
P
PeterKehoe1-Visitor
1-Visitor
July 17, 2012
Question

ModelManager won't reconnect after LAN disruption

  • July 17, 2012
  • 2 replies
  • 4372 views

Is this normal? I have my computer set to go to sleep after being idle for a while. If I was connected to the ModelManager database before it goes to sleep, the connection is lost when I get back to my computer. What I found is that my computer turns off the LAN card when it goes to sleep (to save power). If I turn that option off, then I don't lose connection to ModelManager.

 

I've also found that if I unplug the LAN cable while I have Modeling and ModelManager running, obviously both stop working. Modeling, however, will automatically reconnect to the license server after I plug the cable back it; ModelManager won't reconnect automatically.


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

2 replies

F
FelipeRosendo1-Visitor
1-Visitor
July 19, 2012

This behavior has been what we found over the years to be "normal". Once you loose connection to either the db server or file server your are actually logged out and there is no auto-reconnect feature in MM.

P
PeterKehoe1-VisitorAuthor
1-Visitor
July 20, 2012

Thanks Felipe. I guess this should be a product enhancement.

M
MaxKublin1-Visitor
1-Visitor
November 29, 2012

There *is* a reason why Modeling and other applications re-establish the connection to the License Server:
The user must be able to save his work - so it is vital to try to re-connect.

On the other side, there *is* a reason why Modelmanager does *not* reconnect to the DB:

When MM starts, it reads the XML + a lot of settings (preferences) from the Database.

The settings influence how a lot of things are initialized in MM.

A "re-connect" of MM is therefore pretty close to re-starting MM - this is the reason why there is no "re-connect" for MM.

Opposed to this, a "re-connect" with a old WM Client makes sense, since the U/I is static and determined by

the startup sequence - no preferences from Database need to be loaded - thefore a re-connect is possible

and available in Classic WM.

You can still sub it the ENH for MM but I think the chance is pretty low that this gets implemented.

Hope this helps.

F
FelipeRosendo1-Visitor
1-Visitor
November 29, 2012

Thanks Max for replying.

Right now the user is left with a forced notice that the connection was lost. If a "re-connect" of MM is pretty close to re-starting MM, why not add in that error dialog a simple push button option to restart? In this way they get the notice plus a simple resolution. If the re-connect does not have a chance as an ENH what about the above alteration?

M
MaxKublin1-Visitor
1-Visitor
November 29, 2012

Hi Felipe,

Good proposal. Submit the ENH and start collecting support from the Community.

- Max

    Terms & ConditionsAccessibility statement