Resolution:
Description:
============
Frequently, multiple versions of ActiveSpaces must be run on the same server during development or migration.

Environment:
===========
All ActiveSpaces version.
All supported hardware and OS.

Symptoms:
========
Messages resembling the following:

[1370709776][6726][1106286912][WARNING][transport][Msg.cpp:58][deserialize] message received from older version or unknown source, bad magic_number=0x2000200
when an agent is started.

Resolution:
==========
Multiple versions of Activespaces may be run on the same server provided you set different environments for each and explicitly configure the metaspace and listen on discovery ports using TCP.  However, you will not be able to connect from one version to the other.

For example, on a Red Hat Linux server with  AS 202 and AS 211 installed, setup two environments:

envas202
     export TIBCO_HOME=/home/&ltuser>/as202
     export AS_HOME=$TIBCO_HOME/as/2.0
     export JAVA_HOME=/usr/java/latest
     export PATH=$JAVA_HOME\bin:$AS_HOME/bin:$PATH
     export LD_LIBRARY_PATH=$AS_HOME/lib
     cd $AS_HOME/bin

Then start an agent with:
as-agent -metaspace "as202" -listen "tcp://&ltIP>:50000" -discovery "tcp://&ltIP>:50000"

envas211
     export TIBCO_HOME=/home/&ltuser>/as211
     export AS_HOME=$TIBCO_HOME/as/2.1
     export JAVA_HOME=/usr/java/latest
     export PATH=$JAVA_HOME\bin:$AS_HOME/bin:$PATH
     export LD_LIBRARY_PATH=$AS_HOME/lib
     cd $AS_HOME/bin
as-agent -metaspace "as211" -listen "tcp://&ltIP>:50001" -discovery "tcp://10.240.30.126&ltIP>:50001"

Configuring Multiple ActiveSpaces versions on the same server.