Design and Evaluation of a Fault-Tolerant Mobile-Agent System
IEEE Intelligent Systems
Approaches to fault-tolerant and transactional mobile agent execution---an algorithmic view
ACM Computing Surveys (CSUR)
The agent migration and fault-tolerance management in dynamic network security system
International Journal of Information Technology and Management
Recovery model for free-roaming mobile agent against multiple attacks
Proceedings of the 3rd international conference on Mobile multimedia communications
A novel fault-tolerant execution model by using of mobile agents
Journal of Network and Computer Applications
Efficient algorithms for fault tolerant mobile agent execution
International Journal of High Performance Computing and Networking
Free-roaming mobile agent (FRoMA) protection against multiple attacks
International Journal of Communication Networks and Distributed Systems
Performance analysis of mobile agent failure recovery in e-service applications
Computer Standards & Interfaces
Parallel algorithms for fault-tolerant mobile agent execution
ICA3PP'05 Proceedings of the 6th international conference on Algorithms and Architectures for Parallel Processing
Information Sciences: an International Journal
Hi-index | 0.00 |
Maintaining mobile agent availability in the presence of agent server crashes is a challenging issue since developers normally have no control over remote agent servers. A popular technique is that a mobile agent injects a replica into stable storage upon its arrival at each agent server. However, a server crash leaves the replica unavailable, for an unknown time period, until the agent server is back on-line. This paper uses exception handling to maintain the availability of mobile agents in the presence of agent server crash failures. Two exceptionhandler designs are proposed. The first exists at the agent server that created the mobile agent. The second operates at the previous agent server visited by the mobile agent. Initial performance results demonstrate that although the second design is slower it offers the smaller trip time increase in the presence of agent server crashes.