[ http://issues.apache.org/jira/browse/GERONIMO-1992?page=all ]
Aaron Mulder updated GERONIMO-1992:
-----------------------------------
Description:
If you deploy version 1 of an app, then redeploy version 2, you end up with
version 1 in the repository (unloaded) and version 2 in the repository (loaded
and running).
Then if you redeploy version 3, it dies. I assume it's dying trying to
interact with the unloaded version 1. The stack trace is:
org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
at
org.apache.geronimo.kernel.config.Configuration$$EnhancerByCGLIB$$2c5e9c59.getId(<generated>)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.getResolvedParentIds(SimpleConfigurationManager.java:1133)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.reloadConfiguration(SimpleConfigurationManager.java:721)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.reloadConfiguration(SimpleConfigurationManager.java:709)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(<generated>)
A similar problem comes up in the console, presumably also trying to deal with
the unloaded module:
org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
at
org.apache.geronimo.kernel.config.Configuration$$EnhancerByCGLIB$$d92f9886.getGBeans(<generated>)
at
org.apache.geronimo.kernel.config.Configuration.findGBeanDatas(Configuration.java:692)
at
org.apache.geronimo.kernel.config.Configuration.findGBeanData(Configuration.java:625)
at
org.apache.geronimo.kernel.config.Configuration.findGBean(Configuration.java:610)
at
org.apache.geronimo.kernel.config.Configuration.findGBean(Configuration.java:589)
at
org.apache.geronimo.console.util.KernelManagementHelper.getModuleForConfiguration(KernelManagementHelper.java:527)
at
org.apache.geronimo.console.util.PortletManager.getModule(PortletManager.java:374)
at
org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:141)
To replicate this, deploy an application with no version in the module ID, copy
the directory for it out of the repository, redeploy it to a newer version, and
then copy the old version back into the repository (so it's in the repo but the
server is not aware of it per se).
was:
If you deploy version 1 of an app, then redeploy version 2, you end up with
version 1 in the repository (unloaded) and version 2 in the repository (loaded
and running).
Then if you redeploy version 3, it dies. I assume it's dying trying to
interact with the unloaded version 1. The stack trace is:
org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
at
org.apache.geronimo.kernel.config.Configuration$$EnhancerByCGLIB$$2c5e9c59.getId(<generated>)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.getResolvedParentIds(SimpleConfigurationManager.java:1133)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.reloadConfiguration(SimpleConfigurationManager.java:721)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.reloadConfiguration(SimpleConfigurationManager.java:709)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(<generated>)
> Exception in ConfigManager during redeploy
> ------------------------------------------
>
> Key: GERONIMO-1992
> URL: http://issues.apache.org/jira/browse/GERONIMO-1992
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: kernel
> Versions: 1.1
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Fix For: 1.1
>
> If you deploy version 1 of an app, then redeploy version 2, you end up with
> version 1 in the repository (unloaded) and version 2 in the repository
> (loaded and running).
> Then if you redeploy version 3, it dies. I assume it's dying trying to
> interact with the unloaded version 1. The stack trace is:
> org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
> at
> org.apache.geronimo.kernel.config.Configuration$$EnhancerByCGLIB$$2c5e9c59.getId(<generated>)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.getResolvedParentIds(SimpleConfigurationManager.java:1133)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.reloadConfiguration(SimpleConfigurationManager.java:721)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.reloadConfiguration(SimpleConfigurationManager.java:709)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(<generated>)
> A similar problem comes up in the console, presumably also trying to deal
> with the unloaded module:
> org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
> at
> org.apache.geronimo.kernel.config.Configuration$$EnhancerByCGLIB$$d92f9886.getGBeans(<generated>)
> at
> org.apache.geronimo.kernel.config.Configuration.findGBeanDatas(Configuration.java:692)
> at
> org.apache.geronimo.kernel.config.Configuration.findGBeanData(Configuration.java:625)
> at
> org.apache.geronimo.kernel.config.Configuration.findGBean(Configuration.java:610)
> at
> org.apache.geronimo.kernel.config.Configuration.findGBean(Configuration.java:589)
> at
> org.apache.geronimo.console.util.KernelManagementHelper.getModuleForConfiguration(KernelManagementHelper.java:527)
> at
> org.apache.geronimo.console.util.PortletManager.getModule(PortletManager.java:374)
> at
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:141)
> To replicate this, deploy an application with no version in the module ID,
> copy the directory for it out of the repository, redeploy it to a newer
> version, and then copy the old version back into the repository (so it's in
> the repo but the server is not aware of it per se).
--
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
