geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Forrest Xia (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GERONIMODEVTOOLS-784) EBA Auto-redeployment failed if not enabling hot swap
Date Tue, 14 Feb 2012 04:22:59 GMT

     [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Forrest Xia updated GERONIMODEVTOOLS-784:
-----------------------------------------

    Attachment: org.apache.aries.samples.blueprint.helloworld.assembly_3.0.0.0.eba
    
> EBA Auto-redeployment failed if not enabling hot swap
> -----------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-784
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-784
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 3.0-beta-2
>         Environment: Eclipse indigo sr1
> sun java 6
> Geronimo 3.0-beta-2-snapshot
> GEP trunk
>            Reporter: Forrest Xia
>            Priority: Critical
>         Attachments: org.apache.aries.samples.blueprint.helloworld.assembly_3.0.0.0.eba
>
>
> Steps to reproduce this issue:
> 1. Having these stuffs installed: eclipse indigo sr1, geronimo web profile assembly 3.0-beta-2-snapshot
build, GEP trunk build, IBM OSGi free tool
> 2. Import the attached EBA application into eclipse
> 3. Deploy this application into the server
> 4. Update the wab module to add a new jsp file
> 5. An auto-redeployment will happen to redeploy the changed project into the server,
however, an error message shows as following:
> Module application/org.apache.aries.samples.blueprint.helloworld.assembly/3.0.0-0/eba
already exists in the server.  Try to undeploy it first or use the redeploy command.
> org.apache.geronimo.common.DeploymentException: Module application/org.apache.aries.samples.blueprint.helloworld.assembly/3.0.0-0/eba
already exists in the server.  Try to undeploy it first or use the redeploy command.
> 	at org.apache.geronimo.deployment.Deployer.getConfigID(Deployer.java:320)
> 	at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250)
> 	at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
> 	at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
> 	at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883)
> 	at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
> 	at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344)
>         ...
> If checked all options in "Publish Advanced" tab, then no such exception. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message