How can I replace a JAR file in Integration Server without having to restart the whole server (resulting in a downtime of a few minutes)?
I have multiple JARs deployed to IS under PackageName\code\jars that are used in Java services. If I want to replace an existing JAR with a new version, I can’t remove or replace the old one because it is “blocked” by IS (I guess the JVM holds a reference to the JAR). Stopping the package that contains the JAR doesn’t solve the problem, the file still can’t be removed. I have to restart the whole server and delete/replace the JAR file as soon as the server is down and before the packages are loaded again.
This is a real problem for us, because we run multiple IS deployments daily from our build server and the old JARs cannot be replaced during the deployment. So, after the deployment, the old JARs are still used or even worse the old JAR and the new JAR are both used (if the version number in the file name changed) which results in services that don’t work at all.