I am getting this error when I start up a 3.2.7 server on an AIX machine.
14:38:57,644 WARN [JARDeployer] Failed to add deployable jar: file:/usr/sync40/jboss-3.2.7/server/default/tmp/deploy/tmp41175MANIFEST.MF
java.util.zip.ZipException: Error opening zip file /usr/sync40/jboss-3.2.7/server/default/tmp/deploy/tmp41175MANIFEST.MF
Of course you say, the .MF file is no jar or zip file...
My question is, how can I find out where this .MF file comes from (the .MF which is very happily existing in the tmp folder precisly as the error msg states).
I am a beginner user of JBoss and not that good on the deployment flow.
Any help or tips will be greatly appreciated.
Nevermind, it was simply a folder in the deploy folder that should not exist and which contained only a Manifest file.