Hide Forgot
securitylevel_name: Public After installing Modeshape into BRMS 5.2.0.DEV1 Standalone using the installer, I get the following exception in the log on server startup: 2011-06-10 08:50:09,529 WARN [org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder] (main) Error populating deployment vfsfile:/home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/deploy/modeshape-services.jar/ org.jboss.deployers.spi.DeploymentException: Error populating context vfsfile:/home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/deploy/modeshape-services.jar/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:156) at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:92) at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89) at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1001) at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:437) at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:387) at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:297) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:61) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543) at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:679) Caused by: java.lang.SecurityException: Invalid signature file digest for Manifest main attributes at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:239) at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:193) at java.util.jar.JarVerifier.processEntry(JarVerifier.java:294) at java.util.jar.JarVerifier.update(JarVerifier.java:205) at java.util.jar.JarFile.initializeVerifier(JarFile.java:338) at java.util.jar.JarFile.getInputStream(JarFile.java:403) at org.jboss.virtual.plugins.context.zip.ZipFileWrapper.openStream(ZipFileWrapper.java:222) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.openStream(ZipEntryContext.java:1095) at org.jboss.virtual.plugins.context.zip.ZipEntryHandler.openStream(ZipEntryHandler.java:157) at org.jboss.virtual.VirtualFile.openStream(VirtualFile.java:241) at org.jboss.virtual.VFSUtils.readManifest(VFSUtils.java:280) at org.jboss.virtual.VFSUtils.getManifest(VFSUtils.java:265) at org.jboss.virtual.VFSUtils.addManifestLocations(VFSUtils.java:191) at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:221) at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:139) ... 23 more After this exception, JackRabbit is properly deployed and is usable inside the application. Attaching the complete server log.
Attachment: Added: server.log
Also, this is the output of the installer's Ant build: [lpetrovi@steam modeshape]$ ant Buildfile: /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/modeshape/build.xml determine_home: set-web-home: set-as-home: set-soa-home: init: [echo] JBoss Home is ../jboss-as-web prompt: [input] Enter profile to install ModeShape to: [default] production check: setup.teiid.feature: setup.standard: setup.brms.feature: [copy] Copying 1 file to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/modeshape/resources/runtime/deploy/modeshape-services.jar [copy] Copying 1 file to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/modeshape/resources/runtime/deploy set.jmx.roles.file: set.standard.auth: set.brms.auth: [copy] Copying 1 file to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/modeshape/resources set.auth: [echo] Mapped ModeShape to its domain auth login properties [echo] Set to use jmx-console properties files set.brms.roles.file: set.soa.roles.file: pre.install: install: removeDeployment: [echo] Removed ModeShape from profile: production createDeployment: [echo] adding ModeShape components to production deploy.with.admin: [copy] Copying 77 files to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/deploy [echo] Deloyed with admin console deploy.without.admin: install.modeshape: [copy] Copying 3 files to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/lib [copy] Copying 1 file to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/client [echo] Copied client jar /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/modeshape/client/modeshape-client.jar to ../jboss-as-web/client check.role.exist: [echo] Admin roles: JBossAdmin,HttpInvoker in file ../jboss-as-web/server/production/conf/props/jmx-console-roles.properties [echo] Does role exist ${role.exist} update.roles: patch.login.config: [copy] Copying 1 file to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf [xslt] Processing /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf/login-config.xml to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf/login-config.out [xslt] Loading stylesheet /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/modeshape/resources/temp.xsl [xslt] Processing /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf/login-config.out to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf/login-config.xml [xslt] Loading stylesheet /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/modeshape/resources/pretty-print.xsl [delete] Deleting: /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf/login-config.out [echo] Updated login-config.xml with ${xsl.file} setup.clustering: [copy] Copying 1 file to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf/bindingservice.beans/META-INF [xslt] Processing /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml.out [xslt] Loading stylesheet /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/modeshape/resources/bindings-jboss-beans.xsl [xslt] Processing /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml.out to /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml [xslt] Loading stylesheet /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/modeshape/resources/pretty-print.xsl [delete] Deleting: /home/lpetrovi/QA/BRMS-5.2.0.DEV1.STANDALONE/brms-standalone-5.2.0.dev1/jboss-as-web/server/production/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml.out [echo] Updated bindings-jboss-beans.xml [echo] Enabled Clustering setup: BUILD SUCCESSFUL Total time: 4 seconds
Tested with the latest code updates from ModeShape and the updated build scripts and didn't see the issue. Retest after getting latest.
Still present in BRMS 5.2.0-Dev2. After installing ModeShape and starting the server, the mentioned exception is thrown when deploying ModeShape. This is also happening when deploying to EAP 5.1.
I saw the same thing you did. But, something is strange in the BRMS kitting of modeshape. I took modeshape from the SOA build, which is suppose to be the same bits that BRMS is pulling, and I don't see the same issue. I did find some other issues that I logged, related to security. But didn't have this issue.
Yes, modeshape bits should be the same between SOA-P and BRMS-P except a datasource conf file and a few resteasy jars. I have seen the difference Van mentioned. I think the signature files which generated by MEAD build procedure causes the problem. In BRMS 5.2.0-DEV2, drools and ewp bits are not yet built from MEAD while modeshape is grabbed from MEAD repo which contains the additional signatures. To fix this, I have built 5.2.0-DEV3 which I didn't see the issue any more. See http://jawa05.englab.brq.redhat.com/candidate/BRMS-5.2.0-DEV3/
Verified
Verified fixed in the Dev3 build
Release Notes Text: Added: Verified fixed in the Dev3 build - http://jawa05.englab.brq.redhat.com/candidate/BRMS-5.2.0-DEV3/
I removed the 'technical_note' flag as this appears to be an issue with an internal build so no release note required. Please correct me if I am wrong.