Hi Mark, There are 2 problems in the given ear of this sample application. As a result of those, you are getting this issue. You can fix these issues as given below too.
1. There is a schema problem in the geronimo-application.xml file with G 1.1.1. Comment <context-prority-classloader> element (3 places). 2. If you try to deploy it straight way it won't work :). First you have to create proper ear and war files from the given files. Use jar command to create 3 wars and put them in to a correct package hierachy of a ear file (with applicaion.xml and geronimo-applicaion.xml too). Create the ear file and deploy it. I have informed these issues in to the confuence with a fix (with an Ant script). Hope you will get it soon. Thanks, Lasantha Ranaweera > I'm still stuck on this, and unfortunately I cannot deploy my > applications in production with Geronimo until I get this working. > > Has anyone been able to deploy two different applications to two > different tomcat connectors in the same Geronimo instance? As shown > below, the example on the wiki does not work! > > Thanks, > > -Mark > >> Well, I thought that I might be able to take the example in wiki >> (http://cwiki.apache.org/GMOxDOC11/exposing-web-applications-on- >> distinct-ports.html) and whittle it down to what I need, but I >> can't even deploy the example .ear( appPerPort.ear). I get this error: >> >> geronimo-1.1.1% java -jar bin/deployer.jar deploy appPerPort.ear >> >> Error: Unable to distribute appPerPort.ear: 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=/Users/mark/Programs/geronimo-1.1.1/var/temp/ geronimo- >> deployer4506.tmpdir/appPerPort.ear) >> >> >> and here is the stack trace in the log: >> >> >> Deployer operation failed: 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=/Users/mark/Programs/geronimo-1.1.1/ >> var/temp/geronimo- deployer4504.tmpdir/appperport.ear) >> 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=/Users/mark/ >> Programs/ geronimo-1.1.1/var/temp/geronimo-deployer4504.tmpdir/ >> appperport.ear) 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:122) at >> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke >> (GBeanInstance.java:852) at >> org.apache.geronimo.kernel.basic.BasicKernel.invoke >> (BasicKernel.java:239) at >> org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDe >> pl oy(AbstractDeployCommand.java:106) at >> org.apache.geronimo.deployment.plugin.local.DistributeCommand.run >> (DistributeCommand.java:60) >> >> at java.lang.Thread.run(Thread.java:613) >> >> Any ideas? > > >
