Bug was occuring when running over the new PAMR protocol. Here is an explanation of how to reproduce the bug :
1- Start a PAMR Router
$ ./startRouter.sh
... [addr=/138.96.218.202,localport=33647]
2- Add theses properties on the start of the RM, Scheduler, and Node
proactive.communication.protocol=pamr
proactive.net.router.address=138.96.218.202
proactive.net.router.port=33647
3- Start a node
$ ./startNode.sh node1
...
pamr://0/node1 ...
4 - Start the RM
$ ./startRM.sh
....
pamr://3/ ....
$ ./adminRM.sh -u
pamr://3/
> addnode("
pamr://0/node1","Default")
> listnodes()
5- Start the Scheduler
$ ./startScheduler.sh -u
pamr://3/
...
pamr://6:1099/ ...
$ ./adminScheduler.sh -u
pamr://6/
> submit("/home/bamedro/Experimentations/AmazonEC2/scheduling/samples/jobs_descriptors/Job_8_tasks.xml")
> result(1)
Bug will occur in the RM core console window