[ https://issues.apache.org/jira/browse/GERONIMO-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aman Nanner updated GERONIMO-3208: ---------------------------------- Attachment: nestedjarfile.patch Here is a patch that I use to get around this problem. I'm not sure that this is the best solution to the problem. > In-place deployment fails when renaming file > -------------------------------------------- > > Key: GERONIMO-3208 > URL: https://issues.apache.org/jira/browse/GERONIMO-3208 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment > Affects Versions: 2.0-M6 > Environment: Windows XP SP2 > Reporter: Aman Nanner > Priority: Blocker > Attachments: inplace-deployment-fails.ear.zip, nestedjarfile.patch > > > I am using the latest SNAPSHOT of Geronimo. > I was trying to deploy my custom application with Geronimo using "in-place" > deployment, but it would fail with a ZipException and an "Access denied" > message at the following line: > {code} > System Thread [RMI TCP Connection(189)-192.168.12.66] (Suspended (breakpoint > at line 127 in InPlaceResourceContext)) > InPlaceResourceContext.flush() line: 127 > EARContext(DeploymentContext).flush() line: 428 > TomcatModuleBuilder(AbstractWebModuleBuilder).installModule(JarFile, > EARContext, Module, Collection, ConfigurationStore, Collection) line: 312 > AbstractWebModuleBuilder$$FastClassByCGLIB$$8523248f.invoke(int, > Object, Object[]) line: not available > {code} > So I tried creating a small EAR file for testing purposes, and deployment of > it also failed but at a different point: > {code} > [java] Error: Unable to distribute testing.ear: Problem closing war > context > [java] Cannot rename file > [java] > D:\Development\mx0706\build\geronimo\maintenix\testing.ear\testing.war > [java] to > [java] > D:\Development\mx0706\build\geronimo\maintenix\testing.ear\testing.war.saved > {code} > This failed at line 121 in the {{InPlaceResourceContext}} class. I've > attached the sample EAR file that was causing me this problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.