MWA Multiple Dispatchers Not Working And MWA Server Manager Shows Stopped Status

We notice that, all MWA servers are registering with the first Dispatcher and ignoring any other dispatchers which are up and running.

While starting, we might see messages like below:

MWA Telnet Server Release: 1.0.8.4 [December 12th 2002]
Port Number Dispatcher Will Be Started On: 10763
Port to use for this dispatcher: 10763
Port has probably been taken.
Error starting the Dispatcher.

Or The dispatcher logs might show like below:

Log from first Dispatcher
-------------------------
[Wed Oct 28 16:19:38 2020] runRegistrar: server registry full
[Wed Oct 28 16:19:38 2020] runRegistrar: server registry full
[Wed Oct 28 16:19:38 2020] runRegistrar: server registry full

 Log from second Dispatcher
-----------------------------
[Wed Oct 28 16:17:08 2020] Port to use for this dispatcher: 10300
[Wed Oct 28 16:17:08 2020] main: got local host name 'atgmwa.us.oracle.com'
[Wed Oct 28 16:17:08 2020] main: listener server socket created
[Wed Oct 28 16:17:08 2020] main: created worker threads with connections
[Wed Oct 28 16:17:08 2020] main: created registrar thread
[Wed Oct 28 16:17:08 2020] runRegistrar: registrar server socket created
[Wed Oct 28 16:17:39 2020] main: no servers available
[Wed Oct 28 16:19:42 2020] main: no servers available
[Wed Oct 28 16:19:47 2020] main: no servers available

 It could be happening when you try to configure multiple dispatchers.

Solution:

 1) Shut down all the MWA services including dispatcher

2) Navigate to $ADMIN_SCRIPTS_HOME

cd $ADMIN_SCRIPTS_HOME

3) Edit the mwactl.sh as follows:

FROM:
${MWA_TOP}/bin/MWADIS

TO:
${MWA_TOP}/bin/MWADIS -p "$2"

4) Start MWA services and start dispatchers as below

mwactl.sh start_dispatcher  <port#> &