Re: Geronimo 1.1 Deployment Problem

Dale de los Reyes Mon, 11 Sep 2006 11:23:57 -0700

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 thiswhen the application had some problems in the previous deployment. Bottomline, Geronimo thinks the application is already deployed which it mostlikely is. Use the undeploy feature of the deployer tool. If that stilldoesn't work. You'll need to clean out all the instances oftest.applications/TestApp/1.1/war. This includes the "repository" folderscreated during deployment and the config.xml which you've done before, andpossibly any related files/folders in GERONIMO_HOME/var/temp.

Considering the application deployed fine the first time, but failed on thesubsequent deployment. Here's one possibility that I know of:

Deploying the application in Geronimo console vs. Hot deploy (i.e. copyingthe file to the deploy directory). When I tried deploying the applicationvia the console first, all was fine. "Without undeploying" via the consolefirst, and simply copying the app to the deploy directory. I encountered theerror you mentioned below. I think I also tried it the other way, Hot deploythen Geronimo console (but I don't remember). Anyway, I had to clean out allthe entries and redeploy the application. I now stick with only one type ofdeployment mechanism, Hot deploy, and try not to mix them. This becomes amoot 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 JSPHot

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 theapplication

> 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 ******* deploymy-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 deployedapplication

>>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 deployera

>> > 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 deployera

>> > 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 madeabove.

>> >
>> > -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 deployera

>> > 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. Noticethe

>> > 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 deployera

>> > 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