NetConfig lock not releasing on 5.8

[Paul Mitas]

We are having an issue with the lock on NetConfig and NetMonitor on 5.8.

When you exit the tool correctly it will still say that the monitor or config is locked by a use. It does this if you go File close, or right click on the tab and say close.  Anyone seeing this or now how to fix it?

Topic

[James Cobane]

Paul,

We haven’t seen this issue under 5.8.  Sometimes the common issue is that someone has NetMonitor open (thus the view is locked), so people think that the actual NetConfig is locked; but it’s only the view.  This is true under 5.6 and is still true under 5.8 as well.

When you are opening the ‘NetConfig’, if only the ‘view’ is locked (i.e. someone has NetMonitor open), in the ‘title bar’ of the dialogue box that pops-up, you will see that it indicates ‘Lock Conflict – dflt.mvw’.

Hope this helps.

Jim Cobane

Henry Ford Health

[Paul Mitas]

We are seeing it even when no one has it open. I tried it myself opened netConfig, closed it correctly then opened NetMonitor and got the lock saying I had it.

Not that big a deal just annoying.

Thanks for the help.

[James Cobane]

You could take a look in the $HCISITEDIR/lock directory to see what files are sitting out there, and if you are sure no one is in any of the tools, remove the files.  You may want to verify that permissions are ok on the directory as well.

Jim Cobane

Henry Ford Health

[Russ Ross]

I’ve seen frequent bogus lock warnings in every version of Cloverleaf I’ve ever used but they never kept us from breaking the lock and proceeding.

I don’t know if any enhancement request is already in the wish list but one way to help cloverleaf know if it might need to lock a site is to allow us to proactively choose to launch a site in read mode.

If there is already a way to launch a site in read mode please educate me.

The bogus lock messages for us are so often I have to ignore them altogether.

Russ Ross
RussRoss318@gmail.com

[Russ Ross]

To help us know when something is really locked we have resorted to using our own locking aids by changing the color bar on the IDE and notation on the X-menu on the backend and bitmaps in the netconfig like the screen shot below.

Russ Ross
RussRoss318@gmail.com

[Paul Mitas]

We are able to break the lock, it looks like it is the view that is not being released automatically on exit. It is not that big a deal, if there are any questions we can send a quick note to the person who has the lock.

Thanks all for yur input and suggestions.

Russ where did you get the lock icon, or what did you use to make it?

[Russ Ross]

To create the lock bitmap, I just did a web search for lock pictures and used snagit or hardcopy to grab the picture and saved to hard drive.

Then I used something like MS paint to put the name of each team member on the lock picture and upload to our Cloverleaf bitmap directory so I could have it show up as a choice in the NetConfig drop down.

The one pain was I had to keep playing with sizing the image to make it similar to the size of the HIE bitmap.

So you could start by taking my bitmap lock into MS paint and wiping my name out with yellow and then putting your name on the lock.

I made the files .JPEG when putting them on Cloverleaf.

I created a bitmap lock for each integration team member as seen in the NetConfig drop down attached.

Russ Ross
RussRoss318@gmail.com

[Paul Mitas]

Thanks, I want to make some custom icons but just have not played with it yet to do that.

[Russ Ross]

Also, when doing a cloverleaf upgrade the bitmaps will not get copied forward so you have to copy them forward yourself.

Another choice might be to put inhouse bitmaps in a non cloverleaf directory and use a symbolic link to point to them so they are isolated a little more from the upgrade process.

Russ Ross
RussRoss318@gmail.com

[Jon Blanchard]

This is still a problem in version 6.1.2, and made even worse after we set Open NetConfig as Read Only to true, then false.  The host server is cycled each time.

The lock management functionality needs some improvement.

Migration Consultant
Coffee Regional Medical Center
Eastern Time Zone

[Robert Milfajt]

Russ, love the graphics!     😀

I like the lock notifications, but I would like to offer a suggestion to development team.  If you could remove the locking of the view from both Network Monitor and Network Configurator, that would go a long way to resolving some of these issues.  Most of the time I open Network Configurator, the lock message I get is because someone else has Network Monitor open.  I still have to verify this is true, before I actually break any locks.  If you only allowed Network Monitor tool to lock and manipulate views and Network Configurator to lock and manipulate the configuration that would be awesome.  I know it’s a lot harder than that, but then this is just a suggestion.

Thanks,

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Author]

Replies