When a PROMON -F session is disconnected the database sometimes becomes connectionless and won't shutdown

When a PROMON -F session is disconnected the database sometimes becomes connectionless and won't shutdown
Intermittent connection-less database that fails to shutdown after a PROMON -F session logs out
Any new connection hangs including a new promon -F and utilities (proutil, dbtool), then subsequently does not shut down

At this time, the database is currently running without error and data is being read and written to the database
Even though new users cannot connect the database it is still processing transactions

To recover, all processes have to be killed off and eventually the database broker itself.  

promon option latch counts shows the latch owner, if a user is holding a usr latch.

PROMON -F means not taking out USR latch so that in case of other hangs promon is able to login and dump diagnostic data. 
PROMON -F skips the USR latch during login but acquires a USR latch during logout which it should not:

•  If the USR latch is being held by any other client at the same time, promon -F will appear hung.
•  If the USR latch is not being held by any other client at the same time, any new connections cannot acquire the USR latch in order to gain database access, including PROSHUT to issue a shutdown.

Fixed version(s): OpenEdge 12.4, OpenEdge 11.7.10, OpenEdge 12.2.5

Progress Article:

USR latch remains after user logs out preventing shutdown