[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7199) Seam 2.2.1CR1 + JBDS4M2 + AS6M5 = SHA1 digest error for jdtCompilerAdapter.jar
Rob Stryker (JIRA)
jira-events at lists.jboss.org
Fri Oct 8 01:27:39 EDT 2010
[ https://jira.jboss.org/browse/JBIDE-7199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555993#action_12555993 ]
Rob Stryker commented on JBIDE-7199:
------------------------------------
I am completely unable to replicate this... at all... In any way. In my current environment, which is a JBossTools recent beta1 installation running with runtime workbench (for tracing), seam 2.2.1CR1, and AS6M5. My OS is F12 x64
First of all, I started by creating a seam 2.2.1CR1 web project targeted to AS6. the project is Web, not Ear. I create the project. and publish it to AS-6 (non-started).
1) I open the workspace antlr-runtime.jar and investigate the timestamps there. October 1 2008
2) I open the deployed antlr-runtime.jar and investigate the timestamps. Same. October 1 2008
3) Repeat this for several jars, comparing workspace file timestamps inside jars to the same for deployed jars.
4) I notice no difference at all.
5) I start the server (maybe the server is doing this??)
6) Still no changes noticed
7) I full-publish again, just to see if perhaps publishing to a started server changes file timestamps
8) No change
9) Perhaps this is specific to jdtCompilerAdapter.jar, let's find that jar.
10) Is it in AS6M5? Let's check
[rob at localhost jboss-6.0.0.20100911-M5]$ du -a | grep "jdtCompilerAdapter.jar"
16 ./server/default/tmp/vfs/automount617a847157abbf6/core.jar-bbdaf169ad86ca7e/contents/jdtCompilerAdapter.jar
So it's in the tmp folder of the AS. How did it get there? Where is the jar coming from? Is it in the seam project in the workspace at all?
[rob at localhost SeamPro]$ du -a | grep "jdt"
4 ./.settings/org.eclipse.jdt.core.prefs
Nope. Maybe it's contributed by the seam framework? Let's check.
[rob at localhost jboss-seam-2.2.1.CR1]$ du -a | grep "jdt"
So by my observations,
1) The files in my project's lib folder are not havin their resources change timestamp at all
2) This is true whether server is started or stopped.
3) The app-server does not have jdtCompilerAdapter.jar
4) The seam framework 2.2.1CR1 does not have the jar.
5) The project in the workspace does not have this jar
6) And the only place I've seen the jar is in a random temp directory, though I do wonder how it got there
[rob at localhost SeamPro]$ grep -R "jdtCompilerAdapter.jar" *
Binary file WebContent/WEB-INF/lib/core.jar matches
It seems to be a jar inside core.jar in the workspace. However after checking my deployment, (/home/rob/apps/eclipse/workspaces/main_code/wtp322runtime/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_6.0_Runtime_Server1286513123474/deploy/SeamPro.war/WEB-INF/lib) and opening core.jar, I am noticing all the same timestamps, identical as in the workspace.
And to polish it off, I am not noticing *ANY* deployment errors, and the web-application loads just fine.
Finally, investigating the code that does the publishing shows that it should not be introspecting or changing the timestamps on any resources inside a jar file. It simply copies the jar file. I am having a hell of a time reproducing this, and I quite simply do not think it is reproducible in my environment. It deploys 100% fine.
> Seam 2.2.1CR1 + JBDS4M2 + AS6M5 = SHA1 digest error for jdtCompilerAdapter.jar
> ------------------------------------------------------------------------------
>
> Key: JBIDE-7199
> URL: https://jira.jboss.org/browse/JBIDE-7199
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS
> Affects Versions: 3.2.0.M2
> Environment: Win 7 Java 1.6 32-bit
> Reporter: Burr Sutter
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 3.2.0.Beta1
>
> Attachments: boot.log, boot.log, server.log, server.log
>
>
> New Seam Web Project - using Seam 2.2.1CR1 to target JBoss AS6 M5, it fails on deployment.
> 10:06:23,314 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Real: name=vfs:///D:/servers/jboss-6.0.0.20100911-M5/server/default/deploy/SeamWebProject1.war state=PreReal mode=Manual requiredState=Real: org.jboss.deployers.spi.DeploymentException: Failed to create web module
> at org.jboss.web.deployers.AbstractWarDeployer.deploy(AbstractWarDeployer.java:461) [:6.0.0.20100911-M5]
> at org.jboss.web.deployers.AbstractWarDeployer.deploy(AbstractWarDeployer.java:106) [:6.0.0.20100911-M5]
> at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [:2.2.0.Alpha7]
> at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.Alpha7]
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha7]
> at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.20100911-M5]
> at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:130) [:0.1.0.Alpha1]
> at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.1.0.Alpha1]
> at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:59) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:94) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.1.0.Alpha1]
> at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.1.0.Alpha1]
> at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.1.0.Alpha1]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_20]
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_20]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_20]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_20]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) [:1.6.0_20]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_20]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20]
> at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
> Caused by: java.lang.SecurityException: SHA1 digest error for jdtCompilerAdapter.jar
> at sun.security.util.ManifestEntryVerifier.verify(ManifestEntryVerifier.java:192) [:1.6.0_20]
> at java.util.jar.JarVerifier.processEntry(JarVerifier.java:212) [:1.6.0_20]
> at java.util.jar.JarVerifier.update(JarVerifier.java:199) [:1.6.0_20]
> at java.util.jar.JarVerifier$VerifierStream.read(JarVerifier.java:449) [:1.6.0_20]
> at java.io.InputStream.read(InputStream.java:85) [:1.6.0_20]
> at org.jboss.vfs.VFSUtils.copyStream(VFSUtils.java:439) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VFSUtils.copyStreamAndClose(VFSUtils.java:398) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VFSUtils.copyStreamAndClose(VFSUtils.java:383) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.spi.JavaZipFileSystem.getFile(JavaZipFileSystem.java:157) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.getPhysicalFile(VirtualFile.java:261) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.web.deployers.AbstractWarDeployer$1.visit(AbstractWarDeployer.java:795) [:6.0.0.20100911-M5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:407) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:395) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.web.deployers.AbstractWarDeployer.getExplodedWarUrl(AbstractWarDeployer.java:808) [:6.0.0.20100911-M5]
> at org.jboss.web.deployers.AbstractWarDeployer.deploy(AbstractWarDeployer.java:374) [:6.0.0.20100911-M5]
> ... 41 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list