Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <1040716775.1137018620774.JavaMail.jira@ajax.apache.org>
Date: Wed, 11 Jan 2006 23:30:20 +0100 (CET)
From: "Sachin Patel (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMODEVTOOLS-39) Publishing failed with
 Module Application_ID already exists in the server
In-Reply-To: <579017606.1136928800742.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39?page=comments#action_12362502 ] 

Sachin Patel commented on GERONIMODEVTOOLS-39:
----------------------------------------------

The WTP bugzilla # is 119237.  Its targeted for 1.0.1.  In the meantime, you can either make the application id's unique, or add the Geronimo facet to the Application Project and this should create a geronimo-application.xml file that contains a unique configID.

I will keep this defect open until 119237 is resolved.

> Publishing failed with Module Application_ID already exists in the server
> -------------------------------------------------------------------------
>
>          Key: GERONIMODEVTOOLS-39
>          URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39
>      Project: Geronimo-Devtools
>         Type: Bug
>  Environment: Windows XP
>     Reporter: Kathy Chan
>     Priority: Critical

>
> I was using the following drivers on Windows XP:
> - WTP 1.0
> - Geronimo 1.0 server 
> - Geronimo 20060109 plugin
> With a new workspace, do the following:
> - install Geronimo 1.0 server runtime
> - create Geronimo server using server tooling
> - start server
> - create hello.html in Web project "a1".  Run on server.
> - create hello.html in Web project "a2".  Run on server.
> You'll get the error:
> Publishing failed
>   Distribution of configuration failed.  See .log for details.
> java.lang.Exception: Module Application_ID already exists in the server.  Try to undeploy it first or use the redeploy command.
> org.apache.geronimo.common.DeploymentException: Module Application_ID already exists in the server.  Try to undeploy it first or use the redeploy command.
> 	at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:235)
> 	at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:102)
> 	at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(<generated>)
> 	at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> 	at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
> 	at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118)
> 	at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835)
> 	at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178)
> 	at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:125)
> 	at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(<generated>)
> 	at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> 	at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
> 	at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118)
> 	at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835)
> 	at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178)
> 	at org.apache.geronimo.kernel.jmx.MBeanServerDelegate.invoke(MBeanServerDelegate.java:117)
> 	at mx4j.remote.rmi.RMIConnectionInvoker.invoke(RMIConnectionInvoker.java:219)
> 	at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:324)
> 	at mx4j.remote.rmi.RMIConnectionProxy.invoke(RMIConnectionProxy.java:34)
> 	at mx4j.remote.rmi.RMIConnectionSubjectInvoker.chain(RMIConnectionSubjectInvoker.java:99)
> 	at mx4j.remote.rmi.RMIConnectionSubjectInvoker.access$000(RMIConnectionSubjectInvoker.java:31)
> 	at mx4j.remote.rmi.RMIConnectionSubjectInvoker$1.run(RMIConnectionSubjectInvoker.java:90)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
> 	at mx4j.remote.MX4JRemoteUtils.subjectInvoke(MX4JRemoteUtils.java:163)
> 	at mx4j.remote.rmi.RMIConnectionSubjectInvoker.subjectInvoke(RMIConnectionSubjectInvoker.java:86)
> 	at mx4j.remote.rmi.RMIConnectionSubjectInvoker.invoke(RMIConnectionSubjectInvoker.java:80)
> 	at $Proxy0.invoke(Unknown Source)
> 	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:221)
> 	at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:324)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:148)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
> 	at java.lang.Thread.run(Thread.java:534)
> 	at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doFail(GeronimoServerBehaviour.java:279)
> 	at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy(GeronimoServerBehaviour.java:224)
> 	at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:200)
> 	at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:188)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596)
> 	at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:799)
> 	at org.eclipse.wst.server.core.internal.Server.publish(Server.java:788)
> 	at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira