Home > Articles > Programming > Java

📄 Contents

  1. The <tt>RealtimeThread</tt> Class
  2. The Real-Time Garbage Collector (RTGC)
  3. Conclusion
  • Print
  • + Share This
Like this article? We recommend

The Real-Time Garbage Collector (RTGC)

The RTGC in Java RTS is a fully concurrent, parallel, mark-and-sweep garbage collector (GC) with no stop-world pauses. By parallel, we mean that it does GC work in multiple worker threads; by concurrent, we mean that it does its work concurrently with application threads. In Java SE, the collector needs to pause all application threads to collect dead objects, which results in unpredictable delays in application execution. With the real-time garbage collector, this doesn't happen.

To do its work efficiently, Java RTS doesn't maintain heap spaces or generations. The entire heap is one large space where application threads and RTGC threads operate side-by-side. Its theory of operation is simple: RTGC threads work at lower priority than application RTTs, thereby never interrupting them when eligible for execution. Your application RTTs will be dispatched ahead of RTGC threads when competing for processor time.

Although there are no stop-world pauses, some per-thread pauses can occur when the RTGC needs to scan an application thread's stack. This amounts to a maximum of less than 200 microseconds of latency, and only when the RTGC is in its marking phase. Overall, the RTGC should never interfere with your application threads, and adjusts its own running characteristics to ensure that enough free memory is produced continuously for your application.

Non-real-time threads (JLTs) run at lower priority than the RTGC, and may experience GC-related latency. To gain true real-time application behavior, you must use RTTs with the heap. In cases where no RTGC-related latency in application execution can be tolerated, the RTSJ and Java RTS allow you to use other areas of the memory than the garbage-collected heap. Let's take a look at these now.

New Memory Models

Java RTS defines two main types of non-heap memory: immortal memory and scoped memory. These memory areas are outside of the control of the garbage collector, and hence objects and their memory are not reclaimed automatically. You must manage these areas and associated objects yourself. Let's begin with immortal memory, represented by the ImmortalMemory class in Java RTS.


There is only one immortal memory region in Java RTS, and objects created within it live for the lifetime of the virtual machine. You must take care when placing objects in this region; once it's filled, the space is never reclaimed. To use immortal memory, you have two choices:

  • Specify it as the memory area in the Schedulable object's constructor (see Listing 4).
  • Obtain a reference to the ImmortalMemory singleton object, call its enter method, and provide a Runnable object as the parameter (see Listing 5).

Listing 4: Creating a Schedulable object to execute in immortal memory.

import javax.realtime.*;
public class MyApp {
    static {
        // Create NHRT

 (within immortal memory)
        RealtimeThread rt = new RealtimeThread(
                null, ImmortalMemory.instance() )
            public void run() {
                // Execute real-time code in immortal memory here...


    public static void main(String[] args) {
        // ...

As these code examples show, the ImmortalMemory singleton object represents the immortal memory region. Also, to enter immortal memory, not only must you provide a Runnable, but you must do so from another Schedulable object, as shown in Listing 5.

Listing 5: Entering Immortal Memory with a Runnable.

import javax.realtime.*;
public class Main extends RealtimeThread {
    class TempGauge implements Runnable {
        public TempGauge() {
            System.out.println("TempGauge class created");

        public void run() {
            MemoryArea memArea = RealtimeThread.getCurrentMemoryArea();
            if ( memArea == ImmortalMemory.instance() )
                System.out.println("Running in Immortal Memory");
                System.out.println("NOT running in Immortal Memory!");

            // ...

            System.out.println("TempGauge terminating");

    public void run() {
        TempGauge temp = new TempGauge();

    public static void main(String[] args) {
        Main app = new Main();


You can use these two common patterns to enter any memory region, including scoped memory. Let's examine this possibility.


In the RTSJ and Java RTS, scoped memory regions are those that you define and create in your application. When a Schedulable object enters scoped memory, all objects created are allocated in this region. Since scoped memory isn't garbage collected, Schedulable objects running in this allocation context are not subject to any RTGC-related latency whatsoever. Also, the objects created within a scoped memory region live for the lifetime of the region. Hence, you must ensure that the region is large enough for the time your Schedulable executes within it.

A scoped memory region is reclaimed once a Schedulable exits it, making it completely available for use again. Let me reiterate: The objects within the scoped memory region are not garbage collected, the entire region is simply marked as available, and its objects are "forgotten." As a result, scoped memory regions are useful when you need to execute time-critical logic in response to an event; or a periodic timer, where you clearly understand the allocation needs of the associated code.

The NoHeapRealtimeThread Class

A NoHeapRealtimeThread (NHRT) is just as it name suggests: a Schedulable object that cannot access the Java heap in any way. This means that code executing within an NHRT cannot allocate from the heap, reference objects that reside in the heap, or even exist within the heap itself. Instead, NHRTs must be created within and execute within immortal memory or a scoped memory region.

Since the NoHeapRealtimeThread class extends RealtimeThread, you create and use objects of this class as you would RTTs. Listing 6 shows a simple example. Here, an NHRT is created in a static initializer. By default, all Class objects, static initializers, and interned strings are created in immortal memory. This makes the code in this listing safe to execute, since it will do so in immortal memory by default.

Listing 6: Creating and starting an NHRT in a static initializer.

import javax.realtime.*;
public class Main {
    static {
        // Create NHRT (within immortal memory)
        NoHeapRealtimeThread nhrt =
                new NoHeapRealtimeThread(
                    null, ImmortalMemory.instance() )
            public void run() {
                // Execute NHRT code here...
                System.out.println("NHRT running");


    public static void main(String[] args) {

The code within the static block in Listing 6 will be executed when the Java RTS virtual machine starts. As a result, any code within the run method will execute immediately within immortal memory.

Asynchronous Events

Event processing is a common task in many applications. Similar to the Java Bean events, the Java RTS asynchronous event handler (AEJ) facility is designed for system- and application-specific events that a real-time application may need to handle. Events that are external to Java RTS are often referred to as happenings. Examples include OS-level events (such as POSIX signals), hardware interrupts, and related functionality (that is, file and network I/O), as well as custom events fired by the application itself.

In Java RTS, two main classes make up the AEH facility:

  • AsyncEvent. An object of this type represents the event itself. In the current implementation of Java RTS, this type of object doesn't contain application-specific event data; it needs to be delivered through other means.
  • AsyncEventHandler. A Schedulable object that's executed by the AEH facility within Java RTS when the related event is fired. This object has associated ReleaseParameters, SchedulingParameters, and MemoryParameters objects, which you populate to indicate how the event handler should be scheduled.

Let's look at a sample application event handler for Java RTS. In this example, we have an RTT that simulates a stock-quote data feed that sends quote updates to interested listeners. The listeners, in this case, are asynchronous event handler objects. The class Stock contains the asynchronous event object (see Listing 7).

Listing 7: The Stock asynchronous event.

class Stock {
    public Stock (String s, double v) {
        symbol = s;
        value = v;
        event = new AsyncEvent();
    public String symbol;
    public double value;
    public AsyncEvent event; 

When an instance of the Stock class is created, an individual AsyncEvent object is created also. Application code that's interested in a particular stock's updates needs to create an AEH and call addHandler on the appropriate stock's AsyncEvent object (see Listing 8).

Listing 8: Adding an AEH to an AsyncEvent object.

public double addListener(String symbol, AsyncEventHandler aeh) {
    for ( int s = 0; s < stocks.length; s++ ) {
        if ( stocks[s].symbol.equalsIgnoreCase(symbol)) {
            return stocks[s].value;
    return -1; // symbol not found

When a stock update occurs (as received by the simulated data feed), the event is fired, which in turn notifies each AEH object of the event (see Listing 9).

Listing 9: Generating an asynchronous event.

class DataFeed implements Runnable {
    Random random = new Random(System.currentTimeMillis());
    public void run() {
        int updates = 0;
        while ( updates++ < 10000 ) {
            // Generate a stock update
            int stock = ...

            // Notify handler(s)


This code, being a simulation, generates a random update every period (much of the code has been omitted here for brevity). The important point is that every AEH that added itself as a handler for a particular stock object will be notified when the call to fire is made. The AEH code itself is straightforward, as shown in Listing 10.

Listing 10: An asynchronous event-handler class.

class Listener extends AsyncEventHandler {
    String symbol;
    public Listener(String symbol) {
        this.symbol = symbol;

    public void handleAsyncEvent() {
        if ( getPendingFireCount() > 1 )
            System.out.println("** Updates Queued ***");

        do {
            double value = getValue(symbol);
                    "Listener(" + symbol + "):\tUpdate for " +
                    symbol + "=" + value + " on thread: " +
        } while ( getAndDecrementPendingFireCount() > 0 );

When the associated event object is fired, the AEH object's handleAsyncEvent method is called by the Java RTS virtual machine. All of this code is executed deterministically at a real-time priority to ensure the timely delivery of events.

If events fire faster than your handler code can process, they will queue up inside the virtual machine. As a result, it's a good idea to implement a do..while loop, as in Listing 10, to ensure that your code doesn't miss a single event. A call to getPendingFireCount that returns a value greater than 1 indicates that events are queued. As each event is processed, a call to getAndDecrementFireCount subtracts from the queued event count and returns the remaining queued events.

A Simple Message Application

As a starting point to more practical examples of how to use Java RTS to solve real-world problems, let's look at a simple HTTP message-processing application. In this example, a very basic HTTP server is implemented with Java RTS, and uses RealtimeThread listener objects to process HTTP requests. As a result, HTTP responses are sent deterministically when each request is received. This example should form the basis for many real-world solutions, as many real-time applications perform some sort of message-processing function.

We begin with the RequestProcessor class, which implements Runnable, and responds to all HTTP requests (see Listing 11).

Listing 11: The HTTP request processor.

public class RequestProcessor implements Runnable {
    private static List pool = new LinkedList();
    private int id = 0;

    public RequestProcessor(int id) {
        this.id = id;

    public void run()  {
        boolean run = true;
        // Wait for a request
        while ( run ) {
            Socket conn;

            synchronized ( pool ) {
                while ( pool.isEmpty() ) {
                    try {
                    catch ( InterruptedException e ) {
                        run = false;
                conn = pool.remove(0);


    private void sendHTTPResponse( Socket conn ) {
        try {
            // Read and respond to the request
            OutputStream os = new BufferedOutputStream(
                                    conn.getOutputStream() );
            Writer out = new OutputStreamWriter( os );

            InputStream is = new BufferedInputStream(
                                    conn.getInputStream() );
            Reader in = new InputStreamReader( is, "ASCII" );

            StringBuffer reqLine = new StringBuffer();
            Integer c;
            while ( true ) {
                c = in.read();
                if ( c == '\r' || c == '\n' )

            Long tid = Thread.currentThread().getId();
            Integer pri = Thread.currentThread().getPriority();

            // Send a message acknowledgement to the sender
            String resp = "MESSAGE ACK";
            out.write("HTTP 1.1 200 OK\r\n");
            out.write("Date: " + new Date() + "\r\n");
            out.write("Server: MSGPROC 1.0\r\n");
            out.write("Content-length: " + resp.length() + "\r\n");
            out.write("Content-type: ASCII\r\n\r\n");
        catch ( Exception e ) {

    public static void processRequest(Socket request) {
        synchronized ( pool ) {
            // Make sure that the request gets queued
            pool.add( request );

            // Notify one of the blocked threads in the pool. The
            // first to wake up will process the request

Each instance of RequestProcessor, which can run in a Thread or RealtimeThread, waits on a shared monitor. This monitor, the static member Pool, is also a list of requests. When signaled, the thread wakes up and attempts to remove a request from the list. If none exists (because another RequestProcessor instance got to it first), the thread loops back and waits on the monitor again. Otherwise, the request is handled, and a response is sent to the requester.

The main class that creates the RequestProcessor objects also creates the associated RealtimeThread instances running at a specific priority, and adds them to a queue (see Listing 12).

Listing 12: A pool of RequestProcessor objects is created.

for ( int i = 0; i < 25; i++ ) {
    PriorityParameters pri =
            new PriorityParameters(boosted + 1);

    RealtimeThread rtt = new RealtimeThread(
                null, null, null,
                null, null, new RequestProcessor(i)  );




Next, a separate RealtimeThread is created to listen on a port (port 80 for HTTP), queue each request as it arrives, and then notify the listening RequestProcessor objects of the new request (see Listing 13).

Listing 13: Processing new requests and handing them off to a RequestProcessor object.

PriorityParameters HiPri =
    new PriorityParameters(
        PriorityScheduler.instance().getMaxPriority() );
RealtimeThread rt = new RealtimeThread(HiPri) {
    public void run() {
        // Listen on server socket here, and assign
        // requests to pooled RTTs
        while ( run ) {
            try {
                Socket request = server.accept();
            catch ( Exception e ) {


The call to the static method RequestProcessor.processRequest signals all objects waiting on the shared monitor that a new request is pending. The first available thread to process the signal will get the request and send a response deterministically.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020