Extending the concurrency model of the real‐time specification for Java

Abstract

SUMMARYThe current RTSJ (Real-Time Specification for Java) threading model is dualized: a programmer has to decide between the high predictability offered by the region-based model and the flexibility offered by the garbage collection. So far, there is no unique type of thread which offers both the high predictability of a non-heap thread and the flexibility of a real-time thread in a single entity. Furthermore, this lack has a serious impact on the programmer who has to deal with new and sometimes non-trivial to use mechanisms, such as specific queues of objects or new types of threads, in order to avoid the priority inversion caused by the garbage collector. In order to tackle the concern properly and provide an improved and more generalized programming model, the authors propose a simple extension to the current threading model named RealtimeThread++, in an attempt to introduce more flexibility in the RTSJ concurrency model. The paper describes the extension from several points of view: (i) the programmer, identifying scenarios that may benefit from it significantly; (ii) the real-time Java technology perspective, identifying changes required in the current real-time virtual machine to support it; and (iii) the accumulated experience, relating empirical results obtained from a software prototype that supports the extension.

A hybrid approach for selecting service‐based real‐time composition algorithms in heterogeneous environments

“…Future works include the analysis and inclusion of the new composition algorithms within the reconfiguration algorithm proposed in [10]; the usage of the selection algorithm within the reconfiguration process; the definition of new figures of merit adapted to the different needs of the users; and further evaluations within iLAND middleware and other scenarios [60,61].…”

Enhancing OSGi with real‐time Java support

“…Therefore, our efforts are going to be directed to produce distributed versions for these services taking into account the remote services introduced by the OSGi framework since version 4.2. The authors also consider the integration of dynamic deployment , enhanced real‐time reconfiguration policies proposed in the iLAND project, and enhanced distribution Java support ) as new service implementations for OSGi.…”

Non‐functional information transmission patterns for distributed real‐time Java

“…The authors are evaluating empirically the performance and adaptation performance that may be expected from a generic distributed manager too. This includes its automatic configuration 49–51 and the use of software and hardware virtual machine optimizations 36, 52–56. The aim is to discern which of them are important from the point of view of an end‐to‐end remote invocation.…”