Community
Participate
Working Groups
org.apache.catalina.startup.TldConfig tldScanJar WARNING: Failed to process JAR [jar:reference:file:<path>/javax.el/javax.el-2.2.0.jar!/null] for TLD files java.io.IOException at org.eclipse.osgi.framework.internal.core.ReferenceInputStream.read(ReferenceInputStream.java:32) at java.io.InputStream.read(Unknown Source) at java.io.InputStream.read(Unknown Source) at sun.net.www.protocol.jar.URLJarFile$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.jar.URLJarFile.retrieve(Unknown Source) at sun.net.www.protocol.jar.URLJarFile.getJarFile(Unknown Source) at sun.net.www.protocol.jar.JarFileFactory.get(Unknown Source) at sun.net.www.protocol.jar.JarURLConnection.connect(Unknown Source) at sun.net.www.protocol.jar.JarURLConnection.getJarFile(Unknown Source) at org.apache.catalina.startup.TldConfig.tldScanJar(TldConfig.java:507) at org.apache.catalina.startup.TldConfig.access$100(TldConfig.java:59) at org.apache.catalina.startup.TldConfig$TldJarScannerCallback.scan(TldConfig.java:332) at org.eclipse.gemini.web.tomcat.internal.BundleDependenciesJarScanner.scanBundleUrl(BundleDependenciesJarScanner.java:127) at org.eclipse.gemini.web.tomcat.internal.BundleDependenciesJarScanner.scanJarUrlConnection(BundleDependenciesJarScanner.java:100) at org.eclipse.gemini.web.tomcat.internal.BundleDependenciesJarScanner.scanBundle(BundleDependenciesJarScanner.java:87) at org.eclipse.gemini.web.tomcat.internal.BundleDependenciesJarScanner.scanDependentBundles(BundleDependenciesJarScanner.java:78) at org.eclipse.gemini.web.tomcat.internal.BundleDependenciesJarScanner.scan(BundleDependenciesJarScanner.java:70) at org.eclipse.gemini.web.tomcat.internal.ChainingJarScanner.scan(ChainingJarScanner.java:45) at org.apache.catalina.startup.TldConfig.execute(TldConfig.java:306)
The implementation of org.eclipse.osgi.framework.internal.core.ReferenceInputStream.read() is /* This method should not be called. */ public int read() throws IOException { throw new IOException(); } I prepared a patch for this issue. Can you review it. Regards Vily
Created attachment 198370 [details] Patch proposal
(In reply to comment #2) > Created attachment 198370 [details] > Patch proposal Change committed, tested and pushed. Commit Id:dde53cacd7a2706c77642b69f58d145b0bb3028c