A Patterns Catalog for RTSJ Software Designs

Benowitz, Ed; Niessner, Albert F.

doi:10.1007/978-3-540-39962-9_55

Cited by 24 publications

(21 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Consequently, some RTSJ design patterns have been proposed in the literature [10][11][12]. Also, additional RTSJ design patterns have been discovered in the course of developing RTZen, and the main goal of this section is to describe them.…”

Section: Rtzen's Design Patternsmentioning

confidence: 99%

“…A Wedge Thread [10,11] is used to prevent the premature reclamation of a scoped memory area by controlling its lifetime. It consists of a real-time thread that enters a scope and blocks, waiting for a signal to exit the area.…”

Section: Summary Of Existing Rtsj Patternsmentioning

confidence: 99%

“…The Memory Pool pattern [10] is a set of instances of a given class preallocated in a specific memory area (e.g., immortal memory). When an instance of this class is requested, an object is taken from the pool and when the instance is no longer needed, it is returned to the pool.…”

Section: Summary Of Existing Rtsj Patternsmentioning

confidence: 99%

“…The Memory Block pattern [10] allows the pooling, via serialization, of objects of varying sizes in a byte array block allocated from immortal memory, thus allowing read and write access from any memory scope and any thread type. When an object is discarded, the memory block makes those bytes available for further use.…”

Section: Summary Of Existing Rtsj Patternsmentioning

confidence: 99%

“…To use memory efficiently, RTSJ applications typically create some pools of recyclable objects, preallocated in specific memory areas such as immortal memory [10].…”

Section: Separation Of Creation and Initializationmentioning

confidence: 99%

See 4 more Smart Citations

RTZen: Highly Predictable, Real-Time Java Middleware for Distributed and Embedded Systems

et al. 2005

View full text Add to dashboard Cite

Abstract. Distributed real-time and embedded (DRE) applications possess stringent quality of service (QoS) requirements, such as predictability, latency, and throughput constraints. Real-Time CORBA, an open middleware standard, allows DRE applications to allocate, schedule, and control resources to ensure predictable end-to-end QoS. The Real-Time Specification for Java (RTSJ) has been developed to provide extensions to Java so that it can be used for real-time systems, in order to bring Java's advantages, such as portability and ease of use, to real-time applications. In this paper, we describe RTZen, an implementation of a Real-Time CORBA Object Request Broker (ORB), designed to comply with the restrictions imposed by RTSJ. RTZen is designed to eliminate the unpredictability caused by garbage collection and improper support for thread scheduling through the use of appropriate data structures, threading models, and memory scopes. RTZen's architecture is also designed to hide the complexities of RTSJ related to distributed programming from the application developer. Empirical results show that RTZen is highly predictable and has acceptable performance. RTZen therefore demonstrates that Real-Time CORBA middleware implemented in real-time Java can meet stringent QoS requirements of DRE applications, while supporting safer, easier, cheaper, and faster development in real-time Java.

show abstract

Section: Rtzen's Design Patternsmentioning

confidence: 99%

Section: Summary Of Existing Rtsj Patternsmentioning

confidence: 99%

Section: Summary Of Existing Rtsj Patternsmentioning

confidence: 99%

Section: Summary Of Existing Rtsj Patternsmentioning

confidence: 99%

“…To use memory efficiently, RTSJ applications typically create some pools of recyclable objects, preallocated in specific memory areas such as immortal memory [10].…”

Section: Separation Of Creation and Initializationmentioning

confidence: 99%

See 3 more Smart Citations

RTZen: Highly Predictable, Real-Time Java Middleware for Distributed and Embedded Systems

et al. 2005

View full text Add to dashboard Cite

show abstract

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

Val¹,

García-Valls²,

Estévez-Ayres³

2010

Concurrency and Computation

View full text Add to dashboard Cite

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.

show abstract