Last updated on DECEMBER 20, 2016
Applies to:Oracle Mobile Application Server - Version 126.96.36.199 to 188.8.131.52 [Release 11.5.10]
Information in this document applies to any platform.
Checked for relevance on 19-MAR-2013
Cannot stop MWA listener via adstpall.sh
MWA Dispatcher and Telnet Servers start up normally using adstrtal.sh script.
However, when shutting down the Applications tier using adstpall.sh, the dispatcher (MWADIS) shuts down normally, but the Telnet servers stay up.
The error message present in the Telnet system logs show:
contact the Web Master or System Administrator.
[Thu Oct 23 08:03:52 CDT 2008] (Thread-10) Could not initialize AppsContext for user apps
When attempting to shut down the Telnet servers with mwactlwrpr.sh using an Applications login
account having an MWA Admin responsibility( such as sysadmin/sysadmin), all MWA servers and dispatchers shut down normally.
Mwactlwrpr.sh does not shut down MWA normally when trying to use the appl manager account, which is the account used by adstrtal.sh.
Steps To Reproduce:
1. With applications (forms/web) tier running, issue adstpall.sh apps/<apps password>.
2. Check status of MWADIS using grep (result: not running).
3. Check status of Telnet clients using grep (result: all MWA ports defined are still in use with active processes).
Cannot use adstpall.sh to shut down MWA processes -- making more work for system administrators/DBAs to maintain environments.
Applied WMS RUP6 patch, MWA patches (2462370, 6506599, 4413055, 2602372, 4207535, 5712178)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms