# UM Cluster Issue for Node A

**URL:** <https://techcommunity.softwareag.com/t/um-cluster-issue-for-node-a/302146>\
**Category:** Forum\
**Tags:** um, universal-messaging, realm\
**Created:** [November 1, 2024, 6:48am UTC](https://techcommunity.softwareag.com/t/um-cluster-issue-for-node-a/302146 "2024-11-01T06:48:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rohit\_Dabas](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/rohit_dabas/32/31811_2.png) [@Rohit\_Dabas](https://techcommunity.softwareag.com/u/Rohit_Dabas)\
**Post date:** [November 1, 2024, 6:48am UTC](https://techcommunity.softwareag.com/t/um-cluster-issue-for-node-a/302146/1 "2024-11-01T06:48:59Z")

</div>

#### webMethods UM 10.15

#### I am trying to create a cluster on UM with 3 active nodes, the cluster runs fine when I have node B & C and it’ll show B as master.

But as soon as I add node A to cluster it’ll not have “Naming → DefaultContext” automatically created under it and same is happening for other two nodes.

If I add node A to cluster it’ll show all 3 as offline. I tried to reinstall node A after uninstalling and deleting the installation directory but still it was same.

I copied data directory from working node C to node A but still in enterprise manager it’s not showing any naming context.

Enterprise manager also gives a pop up to create the JNDI context but then throws error like context already exist on other cluster nodes. If I am trying to delete that on other node with 2 seconds it’s created without any manual steps.

The node A shows offline but other two are online.

When i tried to import/export realm xml, getting timedOutException error but connectivity is working fine from both nodes.  
 ![image](https://global.discourse-cdn.com/techcommunity/optimized/3X/9/a/9aaa560f9c26f49e14cbed036b328bdda0e4bba9_2_690x24.png)

Could anyone please support here to understand how can we fix node A.

Thanks

![image](https://global.discourse-cdn.com/techcommunity/original/3X/b/1/b1b1c59a1a3c0d9c1daf24c5d4247b45ea919d44.png)  
 ![image](https://global.discourse-cdn.com/techcommunity/optimized/3X/4/1/417b5c986e9aab852072932c2f5cadc91a974600_2_690x32.png)

---

<div class="post-metadata">

**Author:** ![engin\_arlak](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/engin_arlak/32/27632_2.png) [@engin\_arlak](https://techcommunity.softwareag.com/u/engin_arlak)\
**Post date:** [November 1, 2024, 3:55pm UTC](https://techcommunity.softwareag.com/t/um-cluster-issue-for-node-a/302146/2 "2024-11-01T15:55:32Z")

</div>

If you already have 2 nodes in the cluster working, you can clone one of the working nodes on VM level and change the host name and/or IP on OS/F5. Or you can instead containerize your cluster. Prod ready containers and helm charts are provided by SoftwareAG/IBM. Once you configure it properly, its much more stable than on prem standalone installations.

---

<div class="post-metadata">

**Author:** ![fornd1311](https://avatars.discourse-cdn.com/v4/letter/f/58f4c7/32.png) [@fornd1311](https://techcommunity.softwareag.com/u/fornd1311)\
**Post date:** [November 2, 2024, 6:46am UTC](https://techcommunity.softwareag.com/t/um-cluster-issue-for-node-a/302146/3 "2024-11-02T06:46:57Z")

</div>

I’ve learnt. Thank you.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [May 1, 2025, 6:47am UTC](https://techcommunity.softwareag.com/t/um-cluster-issue-for-node-a/302146/4 "2025-05-01T06:47:34Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.
