MGW Crashes With Message -- Agent Has Been Identified as a Rogue
(Doc ID 1244874.1)
Last updated on MAY 04, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.2.0.1.0 [Release 10.2 to 11.2]Information in this document applies to any platform.
Symptoms
Oracle Messaging Gateway -- MGW is crashing very often.The MGW logs show:
>>2010-10-18 18:27:49 MGW CmdNotifier 1 TRACE CmdNotifier
closing connection
>>2010-10-18 18:27:49 MGW Engine 0 LOG CmdNotifier
Shutdown message received: rogue agent
>>2010-10-18 18:27:49 MGW Engine 3 TRACE CmdNotifier
proposed exit value: -105, existing exit value: -101
>>2010-10-18 18:27:49 MGW CmdNotifier 1 TRACE CmdNotifier
closing connection
>>2010-10-18 18:27:49 MGW CmdNotifier 1 TRACE CmdNotifier
NotificationProcessor is closed
>>2010-10-18 18:27:49 MGW Engine 0 25 main
Agent is shutting down.
or
Agent is shutting down.
>>2010-10-02 01:57:31 MGW Engine 0 LOG ConfigNotifier
Agent has been identified as a rogue and will be shut down.
>>2010-10-02 01:57:35 MGW AdminMgr 0 EXCEPTION main
oracle.mgw.admin.MgwAdminException: [610] Agent has been identified as a rogue and will be shut down.
at oracle.mgw.admin.AdminMgr.setAgentStateInfo(AdminMgr.java:461)
>>>>>>>>>>>>>>>>
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 |
| Cause |
| Solution |
| References |