Error ActiveSpaces threw exception INVALID_OBJECT (peer_invalid - not connected to metaspace ($spacedef))

Error ActiveSpaces threw exception INVALID_OBJECT (peer_invalid - not connected to metaspace ($spacedef))

book

Article ID: KB0089349

calendar_today

Updated On:

Products Versions
TIBCO ActiveSpaces -
Not Applicable -

Description

Resolution:
INVALID_OBJECT error occurs when the underlying metaspace needs to migrate to a different metaspace. This usually happens when there is network/memory related issues. Network related issues causes a split-brain condition where there could be multiple clusters running independently. Once the network is restored, they will discover each other and the cluster with smaller members will migrate to bigger clusters. This migration causes space references to become invalid, throwing INVALID_OBJECT exceptions.

Make sure to run as-admin /asmm on the same sub-network. or else run as-admin /asmm as a remote client to connect metaspace

Issue/Introduction

Error ActiveSpaces threw exception INVALID_OBJECT (peer_invalid - not connected to metaspace ($spacedef))

Additional Information