Abstract
Modern software systems are often distributed, and object-orientation is a leading paradigm for system modeling and design. We consider an object-oriented concurrency model for distributed systems, based on active objects, asynchronous method calls, and shared futures. This approach is appealing in that it gives rise to massive parallelism while avoiding active waiting and explicit locks, and has a simple semantics.In this paper we show that systems developed using active objects and asynchronous method calls can result in system failure due to over-eager concurrency, which we call flooding. A system may feed an object with more calls than it is able to handle, in some cases even regardless of its processing speed. We refer to this situation as flooding of the object. We distinguish between strong and weak flooding. In particular, the notion of strong flooding could lead to problems such as non-responsive objects, system crash, overfull buffers or massive amounts of lost messages, even in the presence of fair scheduling. We present an algorithm to statically detect strong and weak flooding, and prove the soundness of the algorithm.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: Journal of Logical and Algebraic Methods in Programming
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
