[
https://issues.apache.org/jira/browse/SMX4-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489175#comment-13489175
]
Freeman Fang commented on SMX4-1271:
------------------------------------
This is a known pax-web issue and already get fixed by PAXWEB-338[1]
The upcoming SMX 4.5 release would pick up this fix
[1]http://team.ops4j.org/browse/PAXWEB-338
> WarDeployer tries to load README file
> -------------------------------------
>
> Key: SMX4-1271
> URL: https://issues.apache.org/jira/browse/SMX4-1271
> Project: ServiceMix 4
> Issue Type: Bug
> Components: Assemblies, Bundles
> Affects Versions: 4.4.1
> Reporter: Andruschuk Borislav
> Assignee: Freeman Fang
> Priority: Minor
>
> WarDeployer tries to load README file from deploy folder and fails with
> ZipException. It hides the exception (logs in DEBUG) and rescan folder in
> couple seconds. Thus in debug mode you see how it constantly fails all the
> time in infinite loop, consuming memory and CPU:
> 16:15:58,946 | DEBUG | use-03-06/deploy | WarDeployer |
> 175 - org.ops4j.pax.web.pax-web-deployer - 1.0.3 | 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_27]
> at java.util.zip.ZipFile.<init>(ZipFile.java:127)[:1.6.0_27]
> at java.util.jar.JarFile.<init>(JarFile.java:135)[:1.6.0_27]
> at java.util.jar.JarFile.<init>(JarFile.java:99)[:1.6.0_27]
> at
> org.ops4j.pax.web.deployer.internal.WarDeployer.canHandle(WarDeployer.java:40)[175:org.ops4j.pax.web.pax-web-deployer:1.0.3]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.findListener(DirectoryWatcher.java:475)[7:org.apache.felix.fileinstall:3.3.1.fuse-04-06]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:423)[7:org.apache.felix.fileinstall:3.3.1.fuse-04-06]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:271)[7:org.apache.felix.fileinstall:3.3.1.fuse-04-06]
> I believe README file should be just moved out there or prefixed so deployer
> won't try to load it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
