MWA Multiple Dispatchers Not Working And MWA Server Manager Shows Stopped Status
(Doc ID 1077389.1)
Last updated on FEBRUARY 24, 2023
Applies to:
Oracle Mobile Application Server - Version 11.5.10.2 to 12.2 [Release 11.5.10 to 12.2]Information in this document applies to any platform.
Symptoms
1. All MWA servers are registering with the first Dispatcher and ignoring any other dispatchers which are up and running.
In this Example over 20 MWA Telnet Servers were seen running from the Dispatcher Logs using:
tail -f <port>.dispatcher.log.
Log from first Dispatcher
-------------------------
[<time_stamp>] runRegistrar: server registry full
[<time_stamp>] runRegistrar: server registry full
[<time_stamp>] runRegistrar: server registry full
[<time_stamp>] runRegistrar: server registry full
[<time_stamp>] runRegistrar: server registry full
[<time_stamp>] runRegistrar: server registry full
[<time_stamp>] runRegistrar: server registry full
Log from second Dispatcher
-----------------------------
[<time_stamp>] Port to use for this dispatcher: <port>
[<time_stamp>] main: got local host name '<host>.<domain>'
[<time_stamp>] main: listener server socket created
[<time_stamp>] main: created worker threads with connections
[<time_stamp>] main: created registrar thread
[<time_stamp>] runRegistrar: registrar server socket created
[<time_stamp>] main: no servers available
[<time_stamp>] main: no servers available
[<time_stamp>] main: no servers available
2. The following issue is seen from the Application's Self Service MWA Server Manager:
The dispatcher Status shows "Stopped" while both the dispatcher are up and are able to connect through the dispatcher port.
Changes
Attempted to setup and configure Multiple Dispatchers.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |