"Connection.cpp: 53: Core::Connection::receiveMsg: deserialize_failure" and bad_msg_header - magic_number .

"Connection.cpp: 53: Core::Connection::receiveMsg: deserialize_failure" and bad_msg_header - magic_number .

book

Article ID: KB0086037

calendar_today

Updated On:

Products Versions
TIBCO ActiveSpaces -
Not Applicable -

Description

Resolution:
Description:
===========
How to resolve "Connection.cpp: 53: Core::Connection::receiveMsg: deserialize_failure"  and bad_msg_header - magic_number .


Environment:
===========
AS 2.*.*
All OS

Symptoms:
=========
"The following error message is being displayed t"Connect" command in the as-admin tool:

[2013-03-15 09:34:56:301][4184][3052][WARNING][transport] [Msg.cpp, 58: Core::Msg::deserialize: ]message received from older version or unknown source, bad magic_number=0x2000100
[2013-03-15 09:34:56:301][4184][3052][ERROR][transport] [MessageHandler.cpp, 65: MessageHandler::onDataReceive: ][deserialize_failure]


Cause:
======
Different versions of ActiveSpaces are trying to join the same metaspace.

Resolution:
===========
Message deserialize exception will be thrown if different versions of ActiveSpaces are try to join the same metaspace. Message formats of different AS versions are not compatible and should not be used in the same discovery multicast/unicast.

1).  Install the same version of ActiveSpaces in all environments.

2).  Try to avoid a default discovery URL while connecting to metaspace.

3). Make sure nobody is using the same multicast with a different AS version.

4). Make sure your project runs on an isolated multicast/unicast discovery.

Issue/Introduction

"Connection.cpp: 53: Core::Connection::receiveMsg: deserialize_failure" and bad_msg_header - magic_number .