Design Patterns for RTSJ Application Development

Corsaro, Angelo; Santoro, Corrado

doi:10.1007/978-3-540-30470-8_54

Cited by 16 publications

(16 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The creation of singleton objects is prone to breaking referential integrity in SCJ. The singleton pattern under the scoped memory model of RTSJ has been analyzed in [5]. The solution, which can also be applied to SCJ, consists of explicitly allocating the singleton instance in immortal memory by using the available immortal memory API methods.…”

Section: A Lazy Initializationmentioning

confidence: 99%

Reusable Libraries for Safety-Critical Java

Rios

Schoeberl

2014

2014 IEEE 17th International Symposium on Object/Component/Service-Oriented Real-Time Distributed Computing

View full text Add to dashboard Cite

Abstract-The large collection of Java class libraries is a main factor of the success of Java. However, these libraries assume that a garbage-collected heap is used. Safety-critical Java uses scope-based memory areas instead of a garbage-collected heap. Therefore, the Java class libraries are problematic to use in safety-critical Java.We have identified common programming patterns in the Java class libraries that make them unsuitable for safety-critical Java. We propose ways to improve the libraries to avoid the impact of the identified problematic patterns. We illustrate these changes by implementing a total of five scope-safe classes from commonly used libraries.

show abstract

Section: A Lazy Initializationmentioning

confidence: 99%

Reusable Libraries for Safety-Critical Java

Rios

Schoeberl

2014

2014 IEEE 17th International Symposium on Object/Component/Service-Oriented Real-Time Distributed Computing

View full text Add to dashboard Cite

show abstract

“…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%

“…The Immortal Singleton pattern [12] is a simple adaptation of the classical Singleton pattern [8]. It allows the creation of a unique instance of a class from immortal memory, allowing it to be accessed from any memory area.…”

Section: Summary Of Existing Rtsj Patternsmentioning

confidence: 99%

“…Corsaro et al [12] proposed that exceptions can be initially handled in the local scope. With this approach, the notification of the exceptional condition is encapsulated in a status variable or object and then transferred to an outer scope, where the condition is finally handled, or propagated again to an outer scope.…”

Section: Separation Of Creation and Initializationmentioning

confidence: 99%

“…In this pattern, a factory class that creates exception objects of specified types resides in immortal memory. The Immortal Singleton pattern [12] is used to cache the exception objects in the factory so that they can be reused (i.e., re-thrown). Distinct families of exceptions, such as CORBA system exceptions and application exceptions, are organized into different factories.…”

Section: Separation Of Creation and Initializationmentioning

confidence: 99%

See 2 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

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

Design Patterns for RTSJ Application Development

Cited by 16 publications

References 2 publications

Reusable Libraries for Safety-Critical Java

Reusable Libraries for Safety-Critical Java

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

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

Contact Info

Product

Resources

About