JADE Inter-Platform Mobility Service / News: Recent posts

A new Inter-Platform Mobility Service add-on, which must be considered a *development version* (IPMS-v1.104), for the JADE 3.5 and JADE 3.6 has been released. The major changes of this release are:

* The new transfer migration protocol, called Fragmented Transfer Migration, based on sending the agent fragmented in multiple messages has been included.

* New internal features to ease the development of protocols have been included (ProtocolData structure).... read more

A new Inter-Platform Mobility Service add-on, which must be considered a *development version* (IPMS-v1.103), for the JADE 3.5 and JADE 3.6 has been released. The major changes of this release are:

* A new transfer migration protocol based on REST has been included.

* A default migration protocol can be selected by parameter.

You can download this new add-on from the project website (https://tao.uab.cat/ipmp). Notice that it is compiled using the Java SE 1.5 and that inferior versions of it are not supported. Documentation about the new functions usage is included in the package. For questions write in the project website forum. ... read more

A new Inter-Platform Mobility Service add-on, which must be considered a *development version* (IPMS-v1.101), for the JADE 3.5 has been released. The major changes of this release are:

* Migration implementation according to the IPMA architecture.

* Minor bugfixes.

You can download this new add-on from the project website (https://tao.uab.cat/ipmp). Notice that it is compiled using the Java SE 1.5 and that inferior versions of it are not supported. Documentation about the new functions usage is included in the package. For questions write in the project website forum. ... read more

A new Inter-Platform Mobility Service add-on, which must be considered a *development version* (IPMS-v1.100), for the new JADE 3.5 has released. The major changes of this release are:

* Migration architecture according to [1].

* Two migration strategies provided by two transfer protocols:

* Push migration: Agent code and data are sent together before register the agent into the destination platform.... read more

A new revision of the Inter-Platform Mobility
Service add-on (IPMS-v1.2) for the new JADE 3.5 have been released. The other migration add-ons released up to now do not work with JADE 3.5.

The major changes of this release concern internal issues between the platform and the service about the JAR management that, currently, are not directly visible to the final user.

You can download this new revision from the project website (https://tao.uab.cat/ipmp). Some documentation is included in the package. For questions write on the JADE developers list.

The fifth development release of the future branch 2.x has been published. This is the fifth release using the concept of migration protocols. Changes from the last one:

139460 - Homogenize service commands usage

More internal methods take advantage of the usage of Vertical
and Horizontal commands of Jade services infrastructure.

138860 - Develope a Jar Manager

From now on Jar files involved on migrations are managed
by using a new module called Jar Managed. This new module
is included into the service packages (and can be modified
withouth changing the whole agent platform). New managers
regarding other kinds of code can be developed in the
future.... read more

This new release fixes a bug that happens using the inter-platform mobility service with Java 6.

The fourth development release of the future branch 2.x has been published. This is the fourth release using the concept of migration protocols. Changes from the last one:

138308 - Change the existing Inter-Platform Mobility Service version 1.97 to the last architecture migration proposal based on five mobility steps over a FIPA Request Interaction Protocol.

This new release must be considered as unstable. In order to run it the Jade Snapshot must be used and some classes inside the "jade-replace" folder must be replaced in the agent platform.... read more

The third development release of the future branch 2.x has been published. This is the thrid release to use the concept of migration subprotocols. Changes from the last one:

* Task 133862: Now all protocols are run inside an agent called AgentMobilityManager instead AMS.

* Task 133541: JAR Classloader has been modified in order to fix a problem loading classes by reflection. It is API has some changes to allow loading several classes without having to open an close the JAR file multiple times.... read more

The second development release of the future branch 2.x has been published. This is the second release to use the concept of migration subprotocols. Changes from the last one:

* JAR deletion bug on concurrent agents fixed on Windows (taken from the stable branch)

* Task 131202: Improve AMSInitiator working model

This new release must be considered as unstable. Some documentation will be available in the future. In order to run it the Jade Snapshot must be used and the CodeLocator class must be replaced by the one provided in the distributed package. ... read more

A new JAR deletion bug has been detected when several equally agents migrate concurrently on Windows systems.

The problem comes from the CodeLocator class file inside the JADE agent platform. In order to solve it we must replace the affected class. To do that follow this instructions:

1. Get the JADE agent sources
2. Download the CodeLocator.java file from our download section
3. Go to the /src/jade/core/management folder
4. Overwrite the old file with the downloaded one
5. Recompile the platform... read more

This new release fixes a bug removing temporal JAR files on Windows. The problem was because an unclosed file handler.

It is stronly recommended to update to this new release even if you are not a Windows user.

The new development release of the future branch 2.x has been published. This is the first release to use the concept of migration subprotocols. Some documentation will be available in the future.

This new release must be considered as unstable. In order to run it the Jade Snapshot must be used and the CodeLocator class must be replaced by the one provided in the distributed package.

Feedback must be appreciated.

A bug has been discovered over the JADE platform CodeLocator file. The problem is that when many equal agent instances are concurrently migrating in the platform, the CodeLocator class leave a lot of JAR files undeleted.

As this bug is in a file distributed over the JADE platform (but mainly created by us), we have attached it in the files section.

To replace the file, download the new CodeLocator.java file into /src/jade/core/management/ folder and recompile the platform. Then, the problem must be solved.