IBM Support

webMethods Knowlegebase : Software AG Command Central reports Universal Messaging status unresponsive though it is running and listening (1794754)

Troubleshooting


Problem

User reported issue with Universal Messaging (UM) realm runtime status showing in Command Central (CCE) as "unresponsive".

However, the realm is accessible fine via any UM client, like Enterprise Manager (EM) or Integration Server.

Output of CCE sagcc command:

sagcc get monitoring runtimestatus local Universal-Messaging-umserver

Runtime Status

UNRESPONSIVE

Same status for Universal-Messaging-umserver is shown in SPM UI:

http://localhost:8092/spm/monitoring/state/

which makes it clear that this is SPM (Service Platform Manager)-UM connection issue.

Symptom seen in SPM wrapper.log:

"INFO | jvm 1 | 2019/02/12 15:33:20 | 2019/02/12 15:33:20 DEBUG # NirvanaInterfaceFactoryServiceImpl NirvanaInterfaceFactoryServiceImpl.createRealmNode() for runtime component Universal-Messaging-umserver trying the interface: nhp0 with rname: nhp://0.0.0.0:9000

INFO | jvm 1 | 2019/02/12 15:33:20 | 2019/02/12 15:33:20 DEBUG # NirvanaInterfaceFactoryServiceImpl NirvanaInterfaceFactoryServiceImpl.createRealmNode() for runtime component Universal-Messaging-umserver failed fornhp0; exception: Unable to establish RealmNode connection with nSessionAttributes:conns=1/[[nhp://0.0.0.0:9000/]] :: com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:Realm was still unreachable after max retry count - 0

INFO | jvm 1 | 2019/02/12 15:33:20 | 2019/02/12 15:33:20 ERROR # NirvanaRealmManager Unable to connect to the Command Central interface of the Universal Messaging server umserver.

INFO | jvm 1 | 2019/02/12 15:33:20 | 2019/02/12 15:33:20 DEBUG # NirvanaRealmManager NirvanaRealmManager.getRuntimeStatus(), node not reachable returning status UNRESPONSIVE. process id 5661. runtimeComponent Universal-Messaging-umserver"

Symptom seen in SPM default.log:

"2019/02/12 15:33:20 ERROR # Unable to connect to the Command Central interface of the Universal Messaging server umserver."

There are no connection problem symptoms seen in UM nirvana.log or UMRealmService.log.

Document Location

Worldwide

[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSVYEV","label":"IBM webMethods Integration"},"ARM Category":[{"code":"a8mKe00000000AQIAY","label":"Software AG Universal Messaging (NUM)"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Windows Server 2012"}],"Version":"10.3"},{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSFIWYE","label":"IBM webMethods B2B"},"ARM Category":[{"code":"a8mKe00000000AQIAY","label":"Software AG Universal Messaging (NUM)"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Windows Server 2012"}],"Version":"10.3"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
20 March 2025

UID

ibm17211980