Because each client runs the Java application calls within its own session, activities of each client are separate from any other client. No client can access the static variables of other clients, because the memory is not available across session boundaries. Variables defined as static are local to the client. The underlying server environment hides the details associated with session, network, state, and other shared resource management issues from the Java code. The Oracle JVM maximizes sharing read-only data between clients and emphasizes a minimum amount of per-session incremental footprint, to maximize performance for multiple clients. Every call from a single client is managed within its own session, and calls from each client is handled separately. Within a session, the Oracle JVM manages the scalability of applications.
It appears to the client as if a separate, individual JVM was started for each session, although the implementation is more efficient than this seems to imply. Within a session, the client has its own Java environment. This is referred to as a call.Ĭontinues to work within the session, performing as many calls as required. Within the context of a session, the client performs the following:Ĭonnects to the database and opens a session. Figure 2-1 Java Environment Within Each Database Sessionĭescription of 'Figure 2-1 Java Environment Within Each Database Session'
