Red Hat, Inc.

David Lloyd

Stuart Wade Douglas

James R Perkins, Jr

A system includes a memory, a processor in communication with the memory, and a compiler. The compiler is configured to initialize at least one class for an application at compilation time, start a framework at compilation time, and serialize a framework container of the framework into a native image at compilation time. The processor is configured to run the native image to start the application.

Bootstrapping frameworks from a generated static initialization method for faster booting

Implementations for application-specific log routing are described. An example method may include receiving, by an application server, a log message; responsive to determining that a log router associated with the application server is enabled, identifying a thread context associated with an execution thread that created the log message; responsive to identifying a logger associated with the thread context, forwarding the log message to the logger; and processing the log message by the logger.

Application-specific log routing

A system includes a memory, at least one processor in communication with the memory, a counter, and a scheduler. The scheduler is configured to classify a thread of the pool of threads as a first classification as either available or unavailable. Additionally, the scheduler is configured to classify the pool of threads, based on a counter value from the counter, as a second classification less than a configured core thread pool size, equal to or larger than the configured core thread pool size but less than a maximum core thread pool size, or equal to or larger than the maximum core thread pool size. The scheduler is also configured to classify a resistance factor as a third classification as either within a limit or outside the limit, and schedule a work order based on at least one of the classifications.

Thread pool and task queuing method and system

Embodiments relate to systems and methods for invoking serialized data streams. A requester, such as a client computer, can request a set of data from a proxy server using a marker object containing references to remote data sources. The requester and proxy server can each host a handler object to manage marker objects communicated between the two. After receipt of the data request, the proxy server can communicate with the remote data source to initiate a serialized data stream from the remote data source to the requester. In embodiments, the marker object can indicate that the source data hosted on the remote data server should be transmitted directly to the requester, and be streamed in continuous fashion rather than be divided into pieces of data requiring separate requests. In embodiments, marker objects can be nested within other marker objects to invoke multiple serialized streams.

Invoking serialized data streams

Embodiments relate to systems and methods for a shared object lock under state machine control. An operating system or virtual machine environment can host a set of multiple executing threads, and provide those threads with mutual access to one or more objects such as storage objects, memory objects, or others. The threads can independently request that the object be locked or unlocked, and the locked or unlocked state can be shared between the threads. Rather than communicate with the object(s) directly, in embodiments the threads communicate with a state machine that in turn controls the state of the object(s). When a request to change the state of the object(s) is received, the state machine can permit the object(s) to change between locked, unlocked, or other states based on the current state of the machine and the received message. Contention between threads can be reduced or eliminated.

Growing community of inventors

Belleville, WI, United States of America

David Lloyd