You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Achim Nierbeck (JIRA)" <ji...@apache.org> on 2011/07/20 10:22:57 UTC
[jira] [Commented] (KARAF-750) WarDeployer throws exceptions with
empty container
[ https://issues.apache.org/jira/browse/KARAF-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068217#comment-13068217 ]
Achim Nierbeck commented on KARAF-750:
--------------------------------------
this is not really a bug, though it's annoying.
This is a debug message to let you know that the given file in the deploy folder can not be handled by the war deployer.
So how would you know that a presumably working war file doesn't work out without a logger telling you what's wrong.
So the downside here is that the README file actually does get interpreted by the FileInstaller here.
The only thing I could think of to get rid of this is to tell the FileInstaller to skip the README file, though I'm not sure this
really works :-)
> WarDeployer throws exceptions with empty container
> --------------------------------------------------
>
> Key: KARAF-750
> URL: https://issues.apache.org/jira/browse/KARAF-750
> Project: Karaf
> Issue Type: Bug
> Components: karaf-webcontainer
> Affects Versions: 2.2.2
> Reporter: Alexey Markevich
>
> 1. Change \apache-karaf-2.2.2\etc\org.ops4j.pax.logging.cfg :
> log4j.rootLogger=DEBUG, out, osgi:*
> 2. features:install war
> Result: at \apache-karaf-2.2.2\data\log\karaf.log :
> 11:03:21,359 | DEBUG | raf-2.2.2/deploy | WarDeployer | eb.deployer.internal.WarDeployer 62 | 68 - org.ops4j.pax.web.pax-web-deployer - 1.0.4 | Can't handle file README
> java.util.zip.ZipException: error in opening zip file
> at java.util.zip.ZipFile.open(Native Method)[:1.6.0_26]
> at java.util.zip.ZipFile.<init>(ZipFile.java:127)[:1.6.0_26]
> at java.util.jar.JarFile.<init>(JarFile.java:135)[:1.6.0_26]
> at java.util.jar.JarFile.<init>(JarFile.java:99)[:1.6.0_26]
> at org.ops4j.pax.web.deployer.internal.WarDeployer.canHandle(WarDeployer.java:40)[68:org.ops4j.pax.web.pax-web-deployer:1.0.4]
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.findListener(DirectoryWatcher.java:467)[6:org.apache.felix.fileinstall:3.1.10]
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:415)[6:org.apache.felix.fileinstall:3.1.10]
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:263)[6:org.apache.felix.fileinstall:3.1.10]
> 11:03:22,359 | DEBUG | raf-2.2.2/deploy | WarDeployer | eb.deployer.internal.WarDeployer 62 | 68 - org.ops4j.pax.web.pax-web-deployer - 1.0.4 | Can't handle file README
> java.util.zip.ZipException: error in opening zip file
> at java.util.zip.ZipFile.open(Native Method)[:1.6.0_26]
> at java.util.zip.ZipFile.<init>(ZipFile.java:127)[:1.6.0_26]
> at java.util.jar.JarFile.<init>(JarFile.java:135)[:1.6.0_26]
> at java.util.jar.JarFile.<init>(JarFile.java:99)[:1.6.0_26]
> at org.ops4j.pax.web.deployer.internal.WarDeployer.canHandle(WarDeployer.java:40)[68:org.ops4j.pax.web.pax-web-deployer:1.0.4]
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.findListener(DirectoryWatcher.java:467)[6:org.apache.felix.fileinstall:3.1.10]
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:415)[6:org.apache.felix.fileinstall:3.1.10]
> at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:263)[6:org.apache.felix.fileinstall:3.1.10]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira