Distributed real-time specification for Java

Anderson, Jonathan; Jensen, E. Douglas

doi:10.1145/1167999.1168002

Cited by 43 publications

(26 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Only the local node that generates the request may detect the fault in a deadline. This is an important limitation so that many realistic approaches (like DRTSJ [14] in Level-2) require temporal synchronization among different nodes.…”

Section: ) Common Framework For Prioritiesmentioning

confidence: 99%

“…Constraining this analysis now to only distributed realtime Java, one can see two approaches: one produced by RTZen following the track of RT-CORBA [8] and another followed by the different RT-RMI approaches: RT-RMI York [9][10], RT-RMI UPM [11], RT-RMI UC3M [12], RT-RMI Texas [13], and DRTSJ [14]. In the first case, RTZen has a model to mimic: RT-CORBA; and its implementation is understood as a matter of mapping.…”

Section: Introductionmentioning

confidence: 99%

“…Although some researchers [10] [14] have stated that it should be good that certain information flows from the client to the service in each invocation, a painstaking analysis that takes into consideration the cost of this model is still necessary. In the context of RT-RMI, it should identify which parameters should be transferred and processed once at the server.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Towards Propagation of Non-functional Information in Distributed Real-Time Java

Val

García-Valls

Estévez-Ayres

2010

2010 13th IEEE International Symposium on Object/Component/Service-Oriented Real-Time Distributed Computing

View full text Add to dashboard Cite

Many real-time systems use preemptive priorities in their internals to guarantee certain real-time performance. This includes technologies that range from RTSJ (The RealTime Specification for Java) to middleware like Real-Time CORBA (Common Object Request Broker Architecture) which offers additional models and policies that blend client and server information. This decision makes easier the integration of real-time acceptance tests and dispatching policies in these kinds of infrastructures. In this paper, we analyze different tradeoffs that emerge from the definition of different propagation models for distributed real-time Java. The paper covers technological integration aspects, impact on interfaces, and other practical issues more related to the performance that this model offers to a real-time application.

show abstract

Section: ) Common Framework For Prioritiesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Towards Propagation of Non-functional Information in Distributed Real-Time Java

Val

García-Valls

Estévez-Ayres

2010

2010 13th IEEE International Symposium on Object/Component/Service-Oriented Real-Time Distributed Computing

View full text Add to dashboard Cite

show abstract

“…The Distributed Real Time Specification for Java (DRTSJ) [1] reference implementation is an implementation of the distributable thread abstraction based on Real-Time Java and Java's Remote Method Invocation (RMI) mechanism. The RTSJ-Metascheduler is a scheduling API developed by Jonathan Anderson, which facilitates the implementation of Real-Time Java scheduler objects that work with the RTJVM to provide application level scheduling, similar to the Metascheduler discussed in section 8.1.…”

Section: Drtsj and The Rtsj-metaschedulermentioning

confidence: 99%

“…These uncertainties include both transient and sustained resource overloads (due to context-dependent activity execution times), arbitrary arrival patterns for application activities, and arbitrary node/link failures. 1 Nevertheless, such systems require the strongest possible assurances on activity timeliness behavior that are feasible under the circumstances. Another important distinguishing feature of most of these systems is their relatively long activity execution time magnitudes, compared to those of conventional real-time subsystems-e.g., in the order of milliseconds to minutes.…”

Section: Introductionmentioning

confidence: 99%

Recovering from Distributable Thread Failures with Assured Timeliness in Real-Time Distributed Systems

Curley

Anderson

Ravindran

et al. 2006

2006 25th IEEE Symposium on Reliable Distributed Systems (SRDS'06)

View full text Add to dashboard Cite

This thesis considers the problem of recovering from failures of distributable threads with assured timeliness. When a node hosting a portion of a distributable thread fails, it causes orphans-i.e., thread segments that are disconnected from the thread's root. A termination model is considered for recovering from such failures. In this model the orphans must be detected and cleaned up, and failure-exception notification must be delivered to the farthest, contiguous surviving thread segment for resuming thread execution. Two real-time scheduling algorithms (AUA and HUA) and three distributable thread integrity protocols (TPR, D-TPR and W-TPR) are presented. We show that AUA combined with any of the protocols presented bounds the orphan cleanup and recovery time, thereby bounding thread starvation durations and maximizing the total thread accrued timeliness utility. The algorithms and the protocols are implemented in a real-time middleware that supports distributable threads.The experimental studies with the implementation validate the algorithm/protocols' timebounded recovery property and confirm their effectiveness.

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

Distributed real-time specification for Java

Cited by 43 publications

References 15 publications

Towards Propagation of Non-functional Information in Distributed Real-Time Java

Towards Propagation of Non-functional Information in Distributed Real-Time Java

Recovering from Distributable Thread Failures with Assured Timeliness in Real-Time Distributed Systems

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

Contact Info

Product

Resources

About