Is it possible to shutdown or disconnect a secondary login broker (-m3)

Is it possible to shutdown or disconnect a secondary broker?
Can a secondary login broker (-m3) be disconnected once started ?

PROMON will not stop a secondary broker from the terminate server menu.
There is no functionality built-in the product to terminate a secondary login broker. 

It was determined that the Progress Product is functioning as designed.
 
An enhancement to the product can be requested through the Progress Community via an Ideas submission.  Customer feedback is valuable and Idea submissions are monitored by our Product Management team.  Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release.  Once an Idea is submitted the Progress Software Community will have the opportunity to comment on and vote for the Idea.
 
For detailed information on how to submit an Idea, please refer to Knowledge Base article  How to submit an idea for a Progress product enhancement

A secondary login broker is not intended to be stopped once it is started until the database itself is shutdown.

It may be possible to kill the secondary login broker process, but this may cause the database to crash if the secondary broker is holding any resources needed by the database.

If an attempt to kill the secondary login broker is necessary:

1. Disconnect any remote users connected to the remote servers the secondary login broker has spawned
2. Terminate any remote servers the secondary login broker has spawned. Refer to Article  How to terminate a remote server process?  
3. Block the listening port the secondary broker on the firewall, to prevent any new communication to the broker
4. Send a Kill against the PID of the secondary broker
5. After the broker PID is killed, unblock the port within the firewall.

To find the PID of the secondary login broker use promon: Look for a LOGIN as the type and identify the port (right most column) that the broker is using.  
The second column (PID) of that entry is the PID to kill.

Example:

Sv                                        Pend.   Cur.   Max.   Port
No    Pid  Type       Protocol    Logins  Users  Users  Users    Num
                                                                    
  0  13432 Login      TCP              0      0      0      5   8787
  2   2372 Auto       TCP             16      0      4      5   3000
                                                                    
  1  11144 Login      TCP              0      0      0      5   7878
  3  11804 Auto       TCP              3      0      1      5   3001

In the above example:

The remote user should first be disconnected:
Remote server (3) should first be terminated, before killing the secondary login broker's pid: