atom feed11 messages in net.java.dev.phoneme.advancedRe: running jade mobility with phoneME
FromSent OnAttachments
phon...@mobileandembedded.orgMay 28, 2008 8:39 am 
phon...@mobileandembedded.orgMay 28, 2008 10:47 am 
Hinkmond WongMay 28, 2008 3:34 pm 
phon...@mobileandembedded.orgMay 29, 2008 3:06 am 
phon...@mobileandembedded.orgMay 29, 2008 9:29 am 
phon...@mobileandembedded.orgMay 29, 2008 9:30 am 
Hinkmond WongMay 29, 2008 12:55 pm 
phon...@mobileandembedded.orgMay 31, 2008 9:08 am 
phon...@mobileandembedded.orgJun 2, 2008 9:26 am 
phon...@mobileandembedded.orgJun 2, 2008 9:38 am 
Hinkmond WongJun 2, 2008 12:01 pm 
Subject:Re: running jade mobility with phoneME
From:phon...@mobileandembedded.org (phon@mobileandembedded.org)
Date:May 29, 2008 9:29:18 am
List:net.java.dev.phoneme.advanced

a simple make clean solved the system resources problem
(java.lang.OutOfMemoryError) even if i don't know why..

After having recompiled with the CVM_DEBUG=true, i still have the same error,
with no extra information :

Moving now to location : Main-Container jade.core.mobility.AgentMobility: Error creating agent on destination container.
Abort transfer. A class was not found during de-serialization [nested
java.lang.ClassNotFoundException: [Ljava.lang.Object;]

Jade allows me to create java agents (~objects) , and make them move from one
computer to another one through serialization, maybe wasn't i clear about that.
At present, i am able to send an agent serialized on the PhoneME and
deserialized on the jdk1.4.2_16, but the bug occures when the agent is
deserialized on the PhoneME.

I used to have a bad configuration in /etc/host, but it was raising another
error (host unreachable, DispatcherException...) so i assume both machines can
communicate correctly, and i have to look at PhoneME side rather than Jade side.

Did someone test the de-serialization ? I suppose it would be the next step for
me, or try with another VM, but i have some more critical tasks to do first.

cvm -cp testclasses.zip Test return no error, and the only things i see with the
DEBUG=true are many alignement trap things such as the following, which i
suppose won't help me much Alignment trap: cvm (1007) PC=0x408321a0 Instr=0xe59e1000 Address=0x4683efaf FSR
0x013 [Message sent by forum member 'fpillone' (fpillone)]

http://forums.java.net/jive/thread.jspa?messageID=277299