JAR files that are in the server’s CLASSPATH setting are locked while in use by the system class loader. Consequently, on some platforms such as Windows, you cannot update or overwrite a JAR file while the server is running.
To allow refresh of JAR files that are custom loaded, each class loader instance works with a copy of the JAR files that it has loaded. Each JAR file copy is named jar-name+sequence.jar, where jar-name is the name of the original JAR file and sequence is a sequential number that is used to identify the copy. The JAR file copies are created in the EAServer temp/server-name/sequence subdirectory, where server-name is the name of your server. EAServer deletes these directories and files when you restart the server.
