manifest - JBoss java.io.IOException during deployment -
i building jboss application server module, on jbossas 7.1.1. while trying modify classpath in manifest file, ran error:
12:30:53,097 info [org.jboss.as.server.deployment] (msc service thread 1-4) jbas015876: starting deployment of "mydeployableproject.war" 12:30:53,141 error [org.jboss.msc.service.fail] (msc service thread 1-1) msc00001: failed start service jboss.deployment.unit."mydeployableproject.war".structure: org.jboss.msc.service.startexception in service jboss.deployment.unit."mydeployableproject.war".structure: failed process phase structure of deployment "mydeployableproject.war" @ org.jboss.as.server.deployment.deploymentunitphaseservice.start(deploymentunitphaseservice.java:119) [jboss-as-server-7.1.1.final.jar:7.1.1.final] @ org.jboss.msc.service.servicecontrollerimpl$starttask.startservice(servicecontrollerimpl.java:1811) [jboss-msc-1.0.2.ga.jar:1.0.2.ga] @ org.jboss.msc.service.servicecontrollerimpl$starttask.run(servicecontrollerimpl.java:1746) [jboss-msc-1.0.2.ga.jar:1.0.2.ga] @ java.util.concurrent.threadpoolexecutor$worker.runtask(threadpoolexecutor.java:886) [classes.jar:1.6.0_31] @ java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:908) [classes.jar:1.6.0_31] @ java.lang.thread.run(thread.java:680) [classes.jar:1.6.0_31] caused by: org.jboss.as.server.deployment.deploymentunitprocessingexception: failed manifest deployment "/opt/server/bin/jboss-as-7.1.1.final/standalone/deployments/mydeployableproject.war" @ org.jboss.as.server.deployment.module.manifestattachmentprocessor.deploy(manifestattachmentprocessor.java:73) [jboss-as-server-7.1.1.final.jar:7.1.1.final] @ org.jboss.as.server.deployment.deploymentunitphaseservice.start(deploymentunitphaseservice.java:113) [jboss-as-server-7.1.1.final.jar:7.1.1.final] ... 5 more caused by: java.io.ioexception: invalid header field @ java.util.jar.attributes.read(attributes.java:393) [classes.jar:1.6.0_31] @ java.util.jar.manifest.read(manifest.java:182) [classes.jar:1.6.0_31] @ java.util.jar.manifest.<init>(manifest.java:52) [classes.jar:1.6.0_31] @ org.jboss.vfs.vfsutils.readmanifest(vfsutils.java:216) @ org.jboss.vfs.vfsutils.getmanifest(vfsutils.java:199) @ org.jboss.as.server.deployment.module.manifestattachmentprocessor.deploy(manifestattachmentprocessor.java:69) [jboss-as-server-7.1.1.final.jar:7.1.1.final] ... 6 more
it turns out, slight bug in manifest.mf causing issue. file was:
manifest-version: 1.0 class-path: turns out, bug due there being no space after class-path:. (only space different) works:
manifest-version: 1.0 class-path: hopefully stop others wondering.
Comments
Post a Comment