ACM Home Page
Please provide us with feedback. Feedback
Making stronger and flexible the single parent rule in the real-time specification of Java
Full text PdfPdf (663 KB)
Source ACM International Conference Proceeding Series; Vol. 343 archive
Proceedings of the 6th international workshop on Java technologies for real-time and embedded systems table of contents
Santa Clara, California
SESSION: Extending the RTSJ table of contents
Pages 19-28  
Year of Publication: 2008
ISBN:978-1-60558-337-2
Author
M. Teresa Higuera-Toledano  Universidad Complutense de Madrid, Ciudad Universitaria, Madrid Spain
Sponsors
ACM : Assoc. for Computing Machinery
: Sun Microsystems, Inc.
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 42,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1434790.1434794
What is a DOI?

ABSTRACT

Java is the ideal language for developing embedded distributed real-time applications. However, most Java implementations and tools were designed for workstations and have limitations due to that heritage. Special tools are required to support deployment and effect better integration with target hardware and the real-time requirements of embedded systems. The Real-time Specification for Java (RTSJ) extends the Java memory model through immortal and scoped memory regions to reduce the timing-indeterminism caused by garbage collection. The goal of this paper is to improve the predictability and performance of real-time Java applications according to the new RTSJ Specification Request (JSR-282) 2 and 3 enhancements. The single parent rule, that RTSJ introduces, prevents cyclic use of scoped memory regions. But, since this rule cannot be statically enforced, induces run-time overhead and even nondeterministic behavior of applications (due to race conditions). This paper modifies the single parent rule making it stronger, and allows it violation under some conditions in order to have bidirectional references among objects within two different scopes.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
P. Basanta-Val, M.l García-Valls, I. Estévez-Ayres. "No Heap Remote Objects: Leaving Out Garbage Collection at the Server Side". OTM Workshops 2004: Workshop on Java Technologies for Real-Time and Embedded Systems. 2004.
 
3
E. G. Benowitz, A. F. Niessner. "A Patterns Catalog for RTSJ Software Designs". OTM Workshops 2003: Workshop on Java Technologies for Real-Time and Embedded Systems.
4
 
5
A. Borg, A. J. Wellings. "Reference Objects for RTSJ Memory Areas". OTM Workshops 2003: Workshop on Java Technologies for Real-Time and Embedded Systems.
 
6
A. Corsaro, C. Santoro. "Design Patterns for RTSJ Application Development". OTM Workshops 2004: Workshop on Java Technologies for Real-Time and Embedded Systems.
7
 
8
P. C. Dibble. "Real-time Java Platform Programming". Prentice Hall. 2002.
 
9
 
10
 
11
 
12
JSR-282. "RTSJ version 1.1". Available on-line at http://www.jcp.org/en/jsr/detail?id=282
 
13
F. Pizlo, J. M. Fox, D. Holmes, J. Vitek. "Real-Time Java Scoped Memory: Design Patterns and Semantics". In Proc. 7th IEEE International Symposium on Object Oriented Real-Time Distributed Computing, (ISORC 2004)
 
14
 
15
RTJEG. "The Real-time Java Specification". Version 1.0.1(b). Available on-line at http://www.rtj.org
 
16
Timesys. "JTIME RTSJ 1.0 Extensions User Guide" Available on-line at http://www.timesys.com

Collaborative Colleagues:
M. Teresa Higuera-Toledano: colleagues