2601276 - Failed deployment due to open jar files

The deployment of a custom application's patch fails due to opened jar files.

The SAPJVM Profiler I/O trace shows that java.net.URL.openStream method keeps the jar files open:

sun.net.www.protocol.jar.URLJarFile.<init>(java.net.URL,sun.net.www.protocol.jar.URLJarFile$URLJarFileCloseController)void
sun.net.www.protocol.jar.URLJarFile.getJarFile(java.net.URL,sun.net.www.protocol.jar.URLJarFile$URLJarFileCloseController)java.util.jar.JarFile
sun.net.www.protocol.jar.JarFileFactory.get(java.net.URL,boolean)java.util.jar.JarFile
sun.net.www.protocol.jar.JarURLConnection.connect()void
sun.net.www.protocol.jar.JarURLConnection.getInputStream()java.io.InputStream
java.net.URL.openStream()java.io.InputStream

SAP NetWeaver Application Server Java.

The custom application calls java.net.URL.openStream method.

com.sap.jvm.net.url.openstream.nocache, I/O activities, JVM profiler, profiling, JVM profiling, open jar, opened jar, openstream, Config Tool, configtool, JVM parameter , KBA , BC-JAS-WEB , Web Container, HTTP, JavaMail, Servlets , BC-JAS-DPL , Deployment , BC-JVM , SAP Java Virtual Machine , Problem