Hi Dale, let me try to clarify some of the confusion you specified in your reply.
The application that I have been using to test is the same application. I generated a simple application with just one JSP for testing. Initially, I used the MyEclipse plugin in the Eclipse environment to deploy the application. This process creates the following structure. C:\TestEclipse\eclipse32\geronimo-1.1\deploy\Test.war The "Test.war" directory was created as a result of deploying the application and was placed within Geronimo's "deploy" directory. Keep in mind that this is a very simple application so, there was not "geronimo-web.xml" created initially. Next, I started the server. After some investigation I learned that Geronimo 1.1 differs from Geronimo 1.0 in that it deploys applicaitons differently. Since there was no "geronimo-web.xml" for the application, Geronimo generates the numeric id for the folder to deploy the application to from the "deploy" directory and it ended up in the following directory. C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test So, within the "repository\default" directory above a folder was created by Geronimo named "Test", within that the numeric folders for each deployed occurance of the "Test" applicaiton. Next, I tested the applicaiton via a browser by launching the JSP and observed that it works fine. Then, I made a local change to the JSP and saved it. In Eclipse speak, that causes the changed file (JSP) to be redeployed, meaning that it is copied to the "deploy" directory shown above. Once that happens, Geronimo realizes that a change has been made and hot deploys the application. When the hot deploy occurs, the appropriate messages are displayed on Geronimo's console. As a result of the hot deploy, a new numeric folder structure is created in the "repository\default\Test" directory and Geronimo's "config.xml" is modifed with this new location. Now, when I tested this the new changes were observed. I followed this process three times and on the third attempt Geronimo did not Hot deploy the code correctly and the old changes (one iteration back) was displayed upon testing. Furthermore the cleanup that normally occurs in the "repository\default" directory did not happen. When the server is restarted it throws the exception shown in my post. One of the suggestions was to try and create a deployment descriptor (geronimo-web.xml) for the applicaiton and try it again. I did so, and observed similar results, albeit the numeric folders were not created and the application deployed differently but, the result was essentially the same. So, in order to eliminate Eclipse and the MyEclipse plugin I went through the process again, this time I deployed the JSP from just a standard text editor (not using the Eclipse environment) into the "deploy\Test.war" folder manually. I observed Geronimo exhibit the same behavior as above. Keep in mind that I also renamed the "geronimo-web.xml" to keep the test completely the same. So, my conclusion, the problem is 100% in Geronimo. Hopefully, this clears things up for you, please accept my appology if I confused you. I was trying to be as detailed and accurate with the problem description as possible. Fran Dale de los Reyes wrote: > > Hi Fran, > > Here's my understanding of what you're encountering: > > You mention two types of applications: > default/TestApp/1.0/war > test.applications/TestApp/1.1/war > > I'm assuming that both these applications are very similar (or maybe even > the same thing). > > Previously, the geronimo-web.xml descriptor was unspecified. This resulted > in the application being deployed in the repository as: > default/Test/<system > generated id>/war > > A new folder with a new <system generated id> is created on subsequent > deployments resulting in the application becoming unusable. > > The suggested work around of specifying the full <moduleId> declaration > including the <version> and <type> tags should prevent G1.1 from creating > those system generated ids. Meaning, the application should now be able to > redeploy many times without becoming unstable regardless if it's eclipse > or > not. > > The follow-up message indicated test.applications/TestApp/1.1/war was > unable > to deploy because it already exists. Here's where it gets fuzzy because of > the different names. For now, let's assume this should be > default/TestApp/1.1/war. > > If the geronimo-web.xml descriptor is newly created with the fully > specified > <moduleId> and deployed, you will probably see the "unable to deploy" > message because the previous application, default/TestApp/<system > generated > id>/war, may still deployed on Geronimo. > > If that is the case, Geronimo should be a blank slate before the > application > is deployed with the fully specified <moduleId>. Then subsequent > deployments > and redeployments should all be fine even in eclipse. This was the intent > of > the suggested work-around. If that can get you going again and past the > hurdle you're seeing, their will be much rejoicing. ;) > > However, if the two module names are intended to be different. The comment > regarding Geronimo console vs Hot deploy is suggested as a possible > account > of your observation (app deploys fine the first time, but unable to deploy > the second time). If you favor one type of deployment method and stick > with > it (rather than switching them interchangably), you will be able to > attribute any "unable to deploy" errors to some other culprit. > > As for redeploying with the <system generated id>, is it a bug? (*shrug*) > I'll leave that to wiser heads than mine. =) > > Regards, > Dale > > >>From: Fran Varin <[EMAIL PROTECTED]> >>Reply-To: [email protected] >>To: [email protected] >>Subject: Re: Geronimo 1.1 Deployment Problem >>Date: Mon, 11 Sep 2006 12:10:11 -0700 (PDT) >> >> >>Well, I'm glad to see that someone other than us here are able to create >>the >>problem. The issue that is before us is that we do our development through >>Eclipse. So, changes to an application are hot deployed. We're not using >>build scripts in that sense just for our day to day development activities. >>So, this particular problem is an annoying issue. Especially, since the >>problem did not exist in the previous release (v1.0). We will most likely >>need to come up with some reasonable workaround for our devleoment staff so >>that we can live with this. I really do not want them to have to stay on >>v1.0 for long. However, all of this said, I believe that this is clearly a >>bug a this point ( see my last post, I was able to reproduce the problem >>outside of Eclipse) and what's worse is that it effects a major feature >>that >>I must believe is commonly used. Hopefully, the dev. team picks this up and >>addresses it as a serious problem. :) >> >>Fran >> >> >> >> >> >>Dale de los Reyes wrote: >> > >> > Hi Fran, >> > >> > Your descriptor looks fine. Personally, I also include the <type> tag. >> > Which would be <type>war</type> based on the descriptor below. >> > >> > Regarding the error message, that's certainly strange. I normally see >>this >> > when the application had some problems in the previous deployment. >>Bottom >> > line, Geronimo thinks the application is already deployed which it most >> > likely is. Use the undeploy feature of the deployer tool. If that still >> > doesn't work. You'll need to clean out all the instances of >> > test.applications/TestApp/1.1/war. This includes the "repository" >>folders >> > created during deployment and the config.xml which you've done before, >>and >> > possibly any related files/folders in GERONIMO_HOME/var/temp. >> > >> > Considering the application deployed fine the first time, but failed on >> > the >> > subsequent deployment. Here's one possibility that I know of: >> > >> > Deploying the application in Geronimo console vs. Hot deploy (i.e. >>copying >> > the file to the deploy directory). When I tried deploying the >>application >> > via the console first, all was fine. "Without undeploying" via the >>console >> > first, and simply copying the app to the deploy directory. I >> encountered >> > the >> > error you mentioned below. I think I also tried it the other way, Hot >> > deploy >> > then Geronimo console (but I don't remember). Anyway, I had to clean >> out >> > all >> > the entries and redeploy the application. I now stick with only one >> type >> > of >> > deployment mechanism, Hot deploy, and try not to mix them. This becomes >>a >> > moot point once the build is automated, but I digress. >> > >> > Regards, >> > Dale >> > >> > >> >>From: Fran Varin <[EMAIL PROTECTED]> >> >>Reply-To: [email protected] >> >>To: [email protected] >> >>Subject: Re: Geronimo 1.1 Deployment Problem >> >>Date: Mon, 11 Sep 2006 05:32:01 -0700 (PDT) >> >> >> >> >> >>Thanks for the reply, >> >>I added a geronimo-web.xml that looks like: >> >> >> >><?xml version="1.0" encoding="UTF-8"?> >> >><web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1";> >> >> <environment> >> >> <moduleId> >> >> <groupId>test.applications</groupId> >> >> <artifactId>TestApp</artifactId> >> >> <version>1.1</version> >> >> </moduleId> >> >> </environment> >> >> <context-root>/Test</context-root> >> >></web-app> >> >> >> >> >> >> >> >>The application works fine the first time. That is to say that Geronimo >> >>deploys the application fine. But, when I make a modification to the >> JSP >> >>Hot >> >>Deploy fails with the following exception: >> >> >> >>08:26:39,848 INFO [Hot Deployer] Redeploying Test.war >> >>08:26:40,237 ERROR [Hot Deployer] Unable to undeploy >> >>C:\TestEclipse\eclipse32\geronimo-1.1\deploy\Test.war(test.applications/TestApp/1.1/war)Module >> >>test.applications/TestApp/1.1/war already exists in the server. Try to >> >>undeploy it first or use the redeploy command. >> >>org.apache.geronimo.common.DeploymentException: Module >> >>test.applications/TestApp/1.1/war already exists in the server. Try to >> >>undeploy it first or use the redeploy command. >> >> at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254) >> >> 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.doDeploy(AbstractDeployCommand.java:106) >> >> at >> >>org.apache.geronimo.deployment.plugin.local.RedeployCommand.redeployUpdatedConfiguration(RedeployCommand.java:135) >> >> at >> >>org.apache.geronimo.deployment.plugin.local.RedeployCommand.run(RedeployCommand.java:104) >> >> at java.lang.Thread.run(Thread.java:534) >> >> >> >> >> >> >> >>It seems odd to me that the exception seems to be saying that the >> module >> >>already exists when it is trying to redeploy the app. I think this is a >>bug >> >>with Geronimo. >> >> >> >>Fran >> >> >> >> >> >> >> >>Dale de los Reyes wrote: >> >> > >> >> > Hello Fran, >> >> > >> >> > There was a mention in the docs that if the <version> tag is not >> >> > specified, >> >> > Geronimo will default to a system generated value. FWIW, my own >> >> > observation >> >> > is that G1.1 will generate a new folder each time the application is >> >> > deployed and each with a new system generated value. If the >> <version> >> >>tag >> >> > is >> >> > not specified. >> >> > >> >> > As a work around you can try putting values for <version> and <type> >>in >> >> > the >> >> > <moduleId> declaration of the geronimo-web.xml descriptor file. This >> >> > should >> >> > prevent Geronimo from generating the new folders each time the >> >>application >> >> > is deployed. >> >> > >> >> > For example: >> >> > >> >> > <dep:environment >> >> > xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1";> >> >> > <dep:moduleId> >> >> > <dep:groupId>default</dep:groupId> >> >> > <dep:artifactId>Test</dep:artifactId> >> >> > <dep:version>1.0</dep:version> >> >> > <dep:type>war</dep:type> >> >> > </dep:moduleId> >> >> > >> >> > <!-- specify the following as needed --> >> >> > <dep:dependencies/> >> >> > <dep:hidden-classes/> >> >> > <dep:non-overridable-classes/> >> >> > </dep:environment> >> >> > >> >> > Hope this helps. >> >> > >> >> > Regards, >> >> > Dale >> >> > >> >> > >> >> >>From: raxpl <[EMAIL PROTECTED]> >> >> >>Reply-To: [email protected] >> >> >>To: [email protected] >> >> >>Subject: Re: Geronimo 1.1 Deployment Problem >> >> >>Date: Sat, 9 Sep 2006 00:37:29 -0700 (PDT) >> >> >> >> >> >> >> >> >>I won't be much help, i don't use hot deployment (found it too flaky >>in >> >> >>earlier releases) >> >> >>but i've been using remote deployment mostly from the command line >> on >>a >> >> >>remote box >> >> >>and that's been very solid...you just use statements like: >> >> >>java -jar deployer.jar --user system --password ******* deploy >> >>my-welcome >> >> >>(my-welcome being the app) and...undeploy. Can be done from the >>admin. >> >> >>console if >> >> >>you want instead. - could be worth trying as an alternative, seems >> >>robust. >> >> >>cheers >> >> >>rich >> >> >> >> >> >> >> >> >> >> >> >>Fran Varin wrote: >> >> >> > >> >> >> > OK, the information below is a repeatable scenario that describes >> >> the >> >> >> > problem we are having. >> >> >> > >> >> >> > >> >> >> > Eclipse Version: >> >> >> > Version: 3.2.0 >> >> >> > Build id: M20060629-1905 >> >> >> > >> >> >> > >> >> >> > MyEclipse Version: >> >> >> > Version: 5.0.1 >> >> >> > Build id: 20060810-5.0.1-GA >> >> >> > >> >> >> > >> >> >> > Geronimo 1.1 >> >> >> > >> >> >> > Problem: >> >> >> > Hot deploy fails after thrid attempt causing application to be >> >> >> unusable. >> >> >> > >> >> >> > >> >> >> > Scenario: >> >> >> > 1) Server initializes and creates a copy of the deployed >> >>application >> >> >>in >> >> >> > C:\TestEclipse\eclipse32\geronimo-1.1\repository\default >> >> >> > >> >> >> > - The folder structure that was created is: >> >> >> > >> >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test\1157720883871\Test-1157720883871.war >> >> >> > >> >> >> > - Addionally, the config.xml was updated with the following line: >> >> >> > <module name="default/Test/1157720883871/war"/> >> >> >> > >> >> >> > - The following messages were written to the console as the >> server >> >> >>started >> >> >> > the application: >> >> >> > Geronimo Application Server started >> >> >> > 09:08:03,840 INFO [Hot Deployer] Deploying Test.war >> >> >> > 09:08:04,605 WARN [TomcatModuleBuilder] Web application . does >>not >> >> >> > contain a WEB-INF/geronimo-web.xml deployment plan. This may or >>may >> >> >> not >> >> >> > be a problem, depending on whether you have things like resource >> >> >> > references that need to be resolved. You can also give the >>deployer >> >>a >> >> >> > separate deployment plan file on the command line. >> >> >> > Deployed default/Test/1157720883871/war @ >> >> >> > http://RI150WS311:8080/Test >> >> >> > >> >> >> > -Running the application produced the correct result. >> >> >> > >> >> >> > >> >> >> > >> >> >> > 2) Modified the only JSP in the project and saved. This causes >> the >> >> >> > application change to be hot deployed. >> >> >> > >> >> >> > -The following message was written to the console: >> >> >> > 09:13:56,665 INFO [Hot Deployer] Redeploying Test.war >> >> >> > 09:13:56,962 WARN [TomcatModuleBuilder] Web application . does >>not >> >> >> > contain a WEB-INF/geronimo-web.xml deployment plan. This may or >>may >> >> >> not >> >> >> > be a problem, depending on whether you have things like resource >> >> >> > references that need to be resolved. You can also give the >>deployer >> >>a >> >> >> > separate deployment plan file on the command line. >> >> >> > 09:13:57,619 INFO [DirectoryMonitor] Hot deployer notified that >>an >> >> >> > artifact was removed: default/Test/1157720883871/war >> >> >> > Redeployed default/Test/1157721236962/war >> >> >> > >> >> >> > -The line in config.xml above was changed to the following: >> >> >> > <module name="default/Test/1157721236962/war"/> >> >> >> > >> >> >> > -The C:\TestEclipse\eclipse32\geronimo-1.1\repository\default >>folder >> >> >> was >> >> >> > changed to the following >> >> >> > >> >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test\1157720883871 >> >> >> > --- Empty >> >> >> > >> >> >> > >> >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test\1157721236962\Test-1157721236962.war >> >> >> > --- Now contains the deployed application with the changes made >> >>above. >> >> >> > >> >> >> > -Running the application produced the correct result. The changes >>to >> >> >> the >> >> >> > JSP were rendered correctly. >> >> >> > >> >> >> > >> >> >> > >> >> >> > 3) Modified the only JSP a second time and saved. >> >> >> > >> >> >> > -The following message appeared on the console: >> >> >> > 09:19:58,413 INFO [Hot Deployer] Redeploying Test.war >> >> >> > 09:19:58,757 WARN [TomcatModuleBuilder] Web application . does >>not >> >> >> > contain a WEB-INF/geronimo-web.xml deployment plan. This may or >>may >> >> >> not >> >> >> > be a problem, depending on whether you have things like resource >> >> >> > references that need to be resolved. You can also give the >>deployer >> >>a >> >> >> > separate deployment plan file on the command line. >> >> >> > 09:19:59,429 INFO [DirectoryMonitor] Hot deployer notified that >>an >> >> >> > artifact was removed: default/Test/1157721236962/war >> >> >> > >> >> >> > -The line in config.xml was changed to: >> >> >> > <module name="default/Test/1157721598741/war"/> >> >> >> > >> >> >> > -The contents of >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default >> >> >> > were changed to: >> >> >> > >> >> >> > >> >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test\1157720883871 >> >> >> > --- Empty >> >> >> > >> >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test\1157721236962 >> >> >> > --- Empty >> >> >> > >> >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test\1157721598741\Test-1157721598741.war >> >> >> > --- Contains the deployed application with the changes made >> above. >> >> >> > >> >> >> > -Running the application produced the correct result. The changes >>to >> >> >> the >> >> >> > JSP were rendered correctly. >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > 4) Modified the only JSP a third time and saved. >> >> >> > >> >> >> > -No additional messages were written to the console. >> >> >> > >> >> >> > -The Line in config.xml was not modified. >> >> >> > >> >> >> > -No additional changes to >> >> >> > C:\TestEclipse\eclipse32\geronimo-1.1\repository\default >> >> >> > >> >> >> > -The deploy directory >> >> >> > C:\TestEclipse\eclipse32\geronimo-1.1\deploy\Test.war has the >> >> correct >> >> >>JSP >> >> >> > change. >> >> >> > >> >> >> > -Running the application does not display the change made to the >> >> JSP. >> >> >>The >> >> >> > previous change is still deployed. >> >> >> > >> >> >> > -Conslusion: Hot deploy was ignored on the Third change. >> >> >> > >> >> >> > >> >> >> > >> >> >> > 5) Stop server --- successful, no error messages >> >> >> > >> >> >> > >> >> >> > >> >> >> > 6) Start server >> >> >> > >> >> >> > -The following is the console log from starting the server. >> Notice >> >>the >> >> >> > exception thrown in relation to the hot deploy failure from the >> >> >> previous >> >> >> > run. >> >> >> > >> >> >> > Booting Geronimo Kernel (in Java 1.4.2_05)... >> >> >> > Module 1/21 geronimo/rmi-naming/1.1/car started in >> >> >> .500s >> >> >> > Module 2/21 geronimo/j2ee-server/1.1/car started in >> >> >> 1.125s >> >> >> > Module 3/21 geronimo/j2ee-security/1.1/car started in >> >> >> 1.000s >> >> >> > Module 4/21 geronimo/axis/1.1/car started in >> >> >> .172s >> >> >> > Module 5/21 geronimo/openejb/1.1/car started in >> >> >> .703s >> >> >> > Module 6/21 geronimo/system-database/1.1/car started in >> >> >> 3.453s >> >> >> > Module 7/21 geronimo/activemq-broker/1.1/car started in >> >> >> 2.032s >> >> >> > Module 8/21 geronimo/activemq/1.1/car started in >> >> >> .953s >> >> >> > Module 9/21 geronimo/tomcat/1.1/car started in >> >> >> 4.094s >> >> >> > Module 10/21 geronimo/geronimo-gbean-deployer/1.1/car started in >> >> >> .516s >> >> >> > Module 11/21 geronimo/j2ee-deployer/1.1/car started in >> >> >> .516s >> >> >> > Module 12/21 geronimo/openejb-deployer/1.1/car started in >> >> >> .656s >> >> >> > Module 13/21 geronimo/client-deployer/1.1/car started in >> >> >> .140s >> >> >> > Module 14/21 geronimo/axis-deployer/1.1/car started in >> >> >> .203s >> >> >> > Module 15/21 geronimo/sharedlib/1.1/car started in >> >> >> .031s >> >> >> > Module 16/21 geronimo/tomcat-deployer/1.1/car started in >> >> >> .156s >> >> >> > Module 17/21 geronimo/welcome-tomcat/1.1/car started in >> >> >> .609s >> >> >> > Module 18/21 geronimo/webconsole-tomcat/1.1/car started in >> >> >> 7.625s >> >> >> > Module 19/21 geronimo/remote-deploy-tomcat/1.1/car started in >> >> >> .485s >> >> >> > Module 20/21 geronimo/hot-deployer/1.1/car started in >> >> >> .640s >> >> >> > Module 21/21 default/Test/1157721598741/war started in >> >> >> .578s >> >> >> > Startup completed in 31 seconds >> >> >> > Listening on Ports: >> >> >> > 1099 0.0.0.0 RMI Naming >> >> >> > 1527 0.0.0.0 Derby Connector >> >> >> > 4201 0.0.0.0 ActiveIO Connector EJB >> >> >> > 4242 0.0.0.0 Remote Login Listener >> >> >> > 8009 0.0.0.0 Tomcat Connector AJP >> >> >> > 8080 0.0.0.0 Tomcat Connector HTTP >> >> >> > 8443 0.0.0.0 Tomcat Connector HTTPS >> >> >> > 9999 0.0.0.0 JMX Remoting Connector >> >> >> > 61616 0.0.0.0 ActiveMQ Message Broker Connector >> >> >> > >> >> >> > Started Application Modules: >> >> >> > EAR: geronimo/webconsole-tomcat/1.1/car >> >> >> > RAR: geronimo/activemq/1.1/car >> >> >> > RAR: geronimo/system-database/1.1/car >> >> >> > WAR: default/Test/1157721598741/war >> >> >> > WAR: geronimo/remote-deploy-tomcat/1.1/car >> >> >> > WAR: geronimo/welcome-tomcat/1.1/car >> >> >> > >> >> >> > Web Applications: >> >> >> > http://RI150WS311:8080/ >> >> >> > http://RI150WS311:8080/Test >> >> >> > http://RI150WS311:8080/console >> >> >> > http://RI150WS311:8080/console-standard >> >> >> > http://RI150WS311:8080/remote-deploy >> >> >> > >> >> >> > Geronimo Application Server started >> >> >> > 09:29:59,175 ERROR [DirectoryMonitor] Unable to scan file >> >> >> > C:\TestEclipse\eclipse32\geronimo-1.1\deploy\Test.war during >> >> >> > initialization >> >> >> > java.lang.IllegalArgumentException: Invalid id: Test >> >> >> > at >> >> >> > >> >>org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:49) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.deployment.hot.DirectoryHotDeployer.getDeploymentTime(DirectoryHotDeployer.java:215) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.deployment.hot.DirectoryMonitor.initialize(DirectoryMonitor.java:233) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.deployment.hot.DirectoryMonitor.run(DirectoryMonitor.java:206) >> >> >> > at java.lang.Thread.run(Thread.java:534) >> >> >> > 09:30:03,175 INFO [Hot Deployer] Deploying Test.war >> >> >> > 09:30:03,612 WARN [TomcatModuleBuilder] Web application . does >>not >> >> >> > contain a WEB-INF/geronimo-web.xml deployment plan. This may or >>may >> >> >> not >> >> >> > be a problem, depending on whether you have things like resource >> >> >> > references that need to be resolved. You can also give the >>deployer >> >>a >> >> >> > separate deployment plan file on the command line. >> >> >> > 09:30:04,737 ERROR [GBeanInstance] Problem in doFail of >> >> >> > >> >> >> >>default/Test/1157722203222/war?J2EEApplication=null,j2eeType=WebModule,name=default/Test/1157722203222/war >> >> >> > java.lang.RuntimeException: java.lang.NullPointerException >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatContainer.removeContext(TomcatContainer.java:327) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.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:817) >> >> >> > at >> >> >> > >> >>org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$4716170d.removeContext(<generated>) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatWebAppContext.doFail(TomcatWebAppContext.java:469) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:1010) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:374) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:512) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:493) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.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:817) >> >> >> > at >> >> >> > >> >>org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$2d60c486.startConfiguration(<generated>) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) >> >> >> > at java.lang.Thread.run(Thread.java:534) >> >> >> > Caused by: java.lang.NullPointerException >> >> >> > at java.io.File.<init>(File.java:180) >> >> >> > at >> >> >> > >> >> >> >>org.apache.catalina.core.StandardContext.getWorkPath(StandardContext.java:1789) >> >> >> > at >> >> >> > >> >> >> >>org.apache.catalina.startup.ContextConfig.destroy(ContextConfig.java:1269) >> >> >> > at >> >> >> > >> >> >> >>org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:281) >> >> >> > at >> >> >> > >> >> >> >>org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) >> >> >> > at >> >> >> > >> >> >> >>org.apache.catalina.core.StandardContext.destroy(StandardContext.java:4419) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatContainer.removeContext(TomcatContainer.java:325) >> >> >> > ... 31 more >> >> >> > 09:30:04,737 ERROR [GBeanInstanceState] Error while starting; >>GBean >> >>is >> >> >>now >> >> >> > in the FAILED state: >> >> >> > >> >> >> >>abstractName="default/Test/1157722203222/war?J2EEApplication=null,j2eeType=WebModule,name=default/Test/1157722203222/war" >> >> >> > java.lang.IllegalArgumentException: addChild: Child name '/Test' >>is >> >> >> not >> >> >> > unique >> >> >> > at >> >> >> > >> >> >> >>org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:749) >> >> >> > at >> >> >> > >> >>org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) >> >> >> > at >> >> >> >>org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:313) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.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:817) >> >> >> > at >> >> >> > >> >>org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$4716170d.addContext(<generated>) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:448) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:374) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:512) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:493) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.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:817) >> >> >> > at >> >> >> > >> >>org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$2d60c486.startConfiguration(<generated>) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) >> >> >> > at java.lang.Thread.run(Thread.java:534) >> >> >> > org.apache.geronimo.kernel.config.LifecycleException: start of >> >> >> > default/Test/1157722203222/war failed >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:529) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:493) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.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:817) >> >> >> > at >> >> >> > >> >>org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$2d60c486.startConfiguration(<generated>) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) >> >> >> > at java.lang.Thread.run(Thread.java:534) >> >> >> > Caused by: >>org.apache.geronimo.kernel.config.InvalidConfigException: >> >> >> > Unknown start exception >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:440) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:512) >> >> >> > ... 12 more >> >> >> > Caused by: >>org.apache.geronimo.gbean.InvalidConfigurationException: >> >> >> > Configuration default/Test/1157722203222/war failed to start due >>to >> >>the >> >> >> > following reasons: >> >> >> > The service >> >> >> > >> >> >> >>J2EEApplication=null,j2eeType=WebModule,name=default/Test/1157722203222/war >> >> >> > did not start because the doStart method threw an exception. >> >> >> > java.lang.IllegalArgumentException: addChild: Child name '/Test' >>is >> >> >> not >> >> >> > unique >> >> >> > at >> >> >> > >> >> >> >>org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:749) >> >> >> > at >> >> >> > >> >>org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) >> >> >> > at >> >> >> >>org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:313) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.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:817) >> >> >> > at >> >> >> > >> >>org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$4716170d.addContext(<generated>) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:448) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:374) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:512) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:493) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.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:817) >> >> >> > at >> >> >> > >> >>org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$2d60c486.startConfiguration(<generated>) >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) >> >> >> > at java.lang.Thread.run(Thread.java:534) >> >> >> > >> >> >> > >> >> >> > at >> >> >> > >> >> >> >>org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:403) >> >> >> > ... 14 more >> >> >> > 09:30:04,847 WARN [Hot Deployer] Unable to start some modules >> for >> >> >> > C:\TestEclipse\eclipse32\geronimo-1.1\deploy\Test.war >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > -The following line was added to the config.xml: >> >> >> > <module load="false" name="default/Test/1157722203222/war"/> >> >> >> > >> >> >> > >> >> >> > -The contents of >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default >> >> >> > were changed to: >> >> >> > >> >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test\1157720883871 >> >> >> > --- Empty >> >> >> > >> >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test\1157721236962 >> >> >> > --- Empty >> >> >> > >> >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test\1157721598741\Test-1157721598741.war >> >> >> > --- Contains the deployed application with the changes made in >>step >> >> 3 >> >> >> > above >> >> >> > >> >> >> > >> >> >> >>C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test\1157722203222\Test-1157722203222.war >> >> >> > --- Contains the deployed application with the changes attempted >>in >> >> >> step >> >> >>4 >> >> >> > above. >> >> >> > >> >> >> > >> >> >> > -The application runs but, displays the changes successfully >> >> deployed >> >> >> in >> >> >> > step 3. >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > Observations: >> >> >> > 1) This scenario has been executed several times and follows the >> >>exact >> >> >> > same sequence each time. So, the number of successful hot >> >> deployments >> >> >> > follows the exact same pattern. >> >> >> > 2) The only work around is to remove all associated lines from >> >> >>config.xml >> >> >> > and to delete the following folder and all of its content: >> >> >> > C:\TestEclipse\eclipse32\geronimo-1.1\repository\default\Test >> >> >> > 3) When observation #2 is performed and the server restarted, the >> >> >> > exception is not thrown, the application is deployed properly >> with >> >>the >> >> >>new >> >> >> > changes intact and runs fine. >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >>-- >> >> >>View this message in context: >> >> >> >>http://www.nabble.com/Geronimo-1.1-Deployment-Problem-tf2234587.html#a6221348 >> >> >>Sent from the Apache Geronimo - Users forum at Nabble.com. >> >> >> >> >> > >> >> > >> >> > >> >> > >> >> >> >>-- >> >>View this message in context: >> >>http://www.nabble.com/Geronimo-1.1-Deployment-Problem-tf2234587.html#a6245754 >> >>Sent from the Apache Geronimo - Users forum at Nabble.com. >> >> >> > >> > >> > >> > >> >>-- >>View this message in context: >>http://www.nabble.com/Geronimo-1.1-Deployment-Problem-tf2234587.html#a6252843 >>Sent from the Apache Geronimo - Users forum at Nabble.com. >> > > > > -- View this message in context: http://www.nabble.com/Geronimo-1.1-Deployment-Problem-tf2234587.html#a6264977 Sent from the Apache Geronimo - Users forum at Nabble.com.
