Errata (pending changes) for RTSJ 1.0.2
- 4/1/2005: The initial memory area of a Java thread created by a real-time thread is not clear from the specification. The initial memory area is the memory area where the Thread object is allocated. This may be heap memory or immortal memory. The relevant passages from the spec are memory semantics 5 and 15, but those semantics do not determine the initial memory area of a Thread so this interpretation was drawn from the behavior of the RI.
- 11/28/2006 The RealtimeSystem.getConcurrentLocksUsed() method's documentation has an internal inconsistency. It says that the method returns the maximum number of locks that have been used concurrently and that it returns the number of locks currently in use.
It should only say it returns the maximum number used.
- 12/13/2006 The second paragraph in the ScopedMemory.joinAndEnter(logic, time) method's description ends with the clause, "the call to
join returns immediately." It should read, "the invocation of
joinAndEnter(logic, time) behaves effectively like
- 12/13/2006 and the third paragraph in the ScopedMemory.joinAndEnter(time) method's description ends with the clause " the call to
joinAndEnter returns immediately." It should read, "the invocation of
joinAndEnter(time) behaves effectively like
- 5/20/2007 "Standard Java Classes" section Thread Groups, item number 2 reads "A Java thread that is created from a real-time thread inherits..." This is replaced with "A Java thread (not a real-time thread) that is created from a real-time thread inherits..."
- 8/31/2007 In ScopedMemory.setPortal(), "java.lang.IllegalThreadStateException - Thrown if the caller is a Java Thread, and object is not null." is replaced with "java.lang.IllegalThreadStateException - Thrown if the caller is a Java Thread."
- In the
POSIXSignalHandler class, the
addHandler(handler) methods throw
IllegalAssignmentError if the handler is in scoped memory.