geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim McConnell (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMODEVTOOLS-174) "Distribution of configuration failed" when attempting to deploy using Geronimo 2.0 adapter
Date Thu, 30 Aug 2007 20:40:30 GMT

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

Tim McConnell updated GERONIMODEVTOOLS-174:
-------------------------------------------

    Affects Version/s:     (was: 2.0)
                       2.1.x
        Fix Version/s: 2.1.x
             Assignee: Tim McConnell

> "Distribution of configuration failed" when attempting to deploy using Geronimo 2.0 adapter
> -------------------------------------------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-174
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-174
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.1.x
>            Reporter: Tom Mutdosch
>            Assignee: Tim McConnell
>             Fix For: 2.1.x
>
>
> Using the following Geronimo 2.0 runtime server and adapter:
> (*) Server: http://people.apache.org/dist/geronimo/eclipse/unstable/servers/geronimo-tomcat6-jee5-2.0-SNAPSHOT-bin.zip

> (*)Server plugins: http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-2.0.0-v20070621.1204-deployable.zip

> Using eclipse WTP, I create a simple Dynamic Web Project targeting Geronimo with a single
HTML file.  When I do a Run on Server I get the following error in an error dialog and my
page does not run.
> Error:
> Distribution of configuration failed. See log for details.
> Cannot deploy the requested application module because no deployer is able to handle
it. This can happen if you have omitted the J2EE deployment descriptor, disabled a deployer
module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server
that does not have EJB support installed. (moduleFile=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\geronimo-deployer1127.tmpdir\geronimoTestEAR.zip)
> org.apache.geronimo.common.DeploymentException: Cannot deploy the requested application
module because no deployer is able to handle it. This can happen if you have omitted the J2EE
deployment descriptor, disabled a deployer module, or if, for example, you are trying to deploy
an EJB module on a minimal Geronimo server that does not have EJB support installed. (moduleFile=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\geronimo-deployer1127.tmpdir\geronimoTestEAR.zip)
> at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:239)
> at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124)
> 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:127)
> at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:863)
> at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
> at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342)
> 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:127)
> at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:863)
> at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
> at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168)
> at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231)
> at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802)
> at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1423)
> at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:96)
> at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1260)
> at java.security.AccessController.doPrivileged(AccessController.java:275)
> at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1363)
> at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:797)
> at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:309)
> at sun.rmi.transport.Transport$1.run(Transport.java:168)
> at java.security.AccessController.doPrivileged(AccessController.java:275)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:164)
> at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:506)
> at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.handleRequest(TCPTransport.java:838)
> at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:912)
> at java.lang.Thread.run(Thread.java:801)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message