geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-1974) Can't "redeploy" a copy of an application using a different version in the module ID
Date Fri, 05 May 2006 17:46:28 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1974?page=all ]

Aaron Mulder updated GERONIMO-1974:
-----------------------------------

    Attachment: 1974-redeploy-improvements.patch

Here's the work in progress.  It fixes most of the problems, except there's still a lingering
problem with redeploying a stopped configuration.  It looks like in thet scenario, the new
configuration is loaded but not started, but the ConfigurationStatus in the ConfigurationModel
isn't put into the loaded state.  Therefore ConfigurationManager.isLoaded returns false, but
ConfigurationManager.load fails because certain GBeans already exist.  In other words, the
heart of the problem appears to be the ConfigurationStatus being out of sync with the actual
status of the configuration.

Dain, if you can review the changes to SimpleConfigurationManager and look into this last
remaining issue, that would be great.

To reproduce, apply the patch, build, and make a symlink "jetty" from the Geronimo tree to
the assembly output and run this sequence:

java -jar jetty/bin/deployer.jar --verbose undeploy welcome-jetty

java -jar jetty/bin/deployer.jar --verbose deploy applications/welcome/target/geronimo-welcome-1.1-SNAPSHOT.war

java -jar jetty/bin/deployer.jar --verbose stop geronimo-welcome-1.1-SNAPSHOT

java -jar jetty/bin/deployer.jar --verbose redeploy applications/welcome/target/geronimo-welcome-1.1-SNAPSHOT.war

(everything up to here appears to work OK)

java -jar jetty/bin/deployer.jar --verbose start geronimo-welcome-1.1-SNAPSHOT
java -jar jetty/bin/deployer.jar --verbose stop geronimo-welcome-1.1-SNAPSHOT
java -jar jetty/bin/deployer.jar --verbose start geronimo-welcome-1.1-SNAPSHOT

The start commands either fail or say the module is already running, and the stop commands
do nothing, but list-modules never shows it as running.  Starting from the console blows up
with the stack trace shown below.  The web URL http://localhost:8080/geronimo-welcome-1.1-SNAPSHOT/
never shows anything.

Redeploy seems to work OK if the original module was running, regardless of whether it had
a module ID with a version and whether you changed the version if it had one.

org.apache.geronimo.kernel.config.LifecycleException: load of default/geronimo-welcome-1.1-SNAPSHOT/1146848427688/war
failed
        at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:300)
        at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:253)
        at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:228)
        at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:110)
 ...
Caused by: org.apache.geronimo.kernel.GBeanAlreadyExistsException: GBean already registered:
geronimo.config:name="default/geronimo-welcome-1.1-SNAPSHOT/1146848427688/war"
        at org.apache.geronimo.kernel.basic.BasicRegistry.register(BasicRegistry.java:88)
        at org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.java:355)
        at org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:141)


> Can't "redeploy" a copy of an application using a different version in the module ID
> ------------------------------------------------------------------------------------
>
>          Key: GERONIMO-1974
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1974
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: console
>     Versions: 1.1
>     Reporter: Prasad Kashyap
>     Assignee: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1
>  Attachments: 1974-redeploy-improvements.patch, redeploy-stacktrace.txt
>
> If you deploy an application with version foo/bar/1.0/baz and then change the plan to
be foo/bar/1.1/baz and try to redeploy it doesn't work.

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


Mime
View raw message