[jboss-jira] [JBoss JIRA] (AS7-141) Deployment fails with empty classpath manifest

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/AS7-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12946958#comment-12946958 ] 

Brian Stansberry commented on AS7-141:
--------------------------------------

Hi Peter,

What you are reporting sounds like a very different issue. Is your ear zipped? That log message occurs when the deployment scanner reads the archive and doesn't find the expected signature bytes that should be present in a proper zip file.[1]

The scanner has no idea what a MANIFEST.MF even is; it sees the zip as a bunch of bytes, opaque other than the various zip format metadata bytes dispersed throughout.

I suspect that changing the MANIFEST.MF had the side effect of correcting whatever the issue was with the zip file. 

I recommend you check the original zip to see if it is in some way faulty. Perhaps some tool like InfoZip can help[2]. (I'm not an expert on such tooling.) If you have an EAP subscription, you can also open a case on the Customer Support Portal.

[1] For the actual scan algorithm see https://github.com/wildfly/wildfly/blob/master/deployment-scanner/src/main/java/org/jboss/as/server/deployment/scanner/ZipCompletionScanner.java
[2] http://en.wikipedia.org/wiki/Infozip
                
> Deployment fails with empty classpath manifest
> ----------------------------------------------
>
>                 Key: AS7-141
>                 URL: https://issues.jboss.org/browse/AS7-141
>             Project: Application Server 7
>          Issue Type: Bug
>    Affects Versions: 7.0.0.Alpha1
>            Reporter: Max Rydahl Andersen
>            Assignee: Stuart Douglas
>             Fix For: 7.0.0.Beta1
>
>         Attachments: jbossas7-deploy-example.war
>
>
> If you war has a MANIFEST.MF with empty classpath you get an error even though empty Class-Path: is present (and afaik valid).
> This is btw. how Eclipse defaults to create a war with no jar dependencies thus it would fail for a lot of folks ;)
> 11:53:53,682 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "jbossas7-deploy-example.war"
> 11:53:53,706 WARN  [org.jboss.vfs] (MSC service thread 1-1) VFS was unable to set the URLStreamHandlerFactory.  This will have unpredictable results
> 11:53:53,731 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001:Failed to start service jboss.deployment.unit."jbossas7-deploy-example.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbossas7-deploy-example.war".PARSE: Failed to process phase PARSE of deployment "jbossas7-deploy-example.war"
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:109)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1367)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
> 	at java.lang.Thread.run(Thread.java:680) [:1.6.0_22]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Class Path entry  in "/content/jbossas7-deploy-example.war"  not found. 
> 	at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.deploy(ManifestClassPathProcessor.java:123)
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:103)
> 	... 4 more
> I'm attaching a simple war showing this.

--
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