Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Java classes, instances, and shared data
On the AR System Administration: Plugin Server Configuration form, you can configure two or more Java plug-in classes in a plug-in set or group. When the Java plug-in server starts, it performs the following actions:
It loads each configured plug-in class or group in a separate class loader.
Any static initialization in the classes is executed.
The Java plug-in server initializes an instance of each plug-in class listed in the AR System Administration: Plugin Server Configuration form for each worker thread in its worker thread pool.
Each time the AR System server makes a connection to the Java plug-in server, a selector thread adds the request associated with the connection to a task queue. As soon as a worker thread is free, it processes the next request in the task queue.
Different instances of a class can share data in the static class variables. To be thread-safe, however, the class implementation must protect this static data. The class can use instance variables to store data that is not shared. Because each thread has a separate instance, this data is thread-safe.
