SAP Knowledge Base Article - Preview

2601276 - Failed deployment due to open jar files

Symptom

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


Read more...

Environment

SAP NetWeaver Application Server Java.

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

Product

SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3

Keywords

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

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.