This issue should be fixed now. Aaron
On 11/11/05, Aaron Mulder <[EMAIL PROTECTED]> wrote: > That's correct, we just fail to remove the entry from config.xml when > we undeploy. This is a known issue. > > Thanks, > Aaron > > On 11/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Here is the output of the java -jar bin\deployer.jar undeploy > > org/apache/geronimo/tools/JMXConsole command: > > > > Module org/apache/geronimo/tools/JMXConsole stopped. > > Module org/apache/geronimo/tools/JMXConsole unloaded. > > Module org/apache/geronimo/tools/JMXConsole uninstalled. > > Undeployed org/apache/geronimo/tools/JMXConsole > > > > Configuration is stopped and then undeployed. > > > > So unless deployer output is lying, the problem is not invalid gbean state > > management, but config.xml corruption on geronimo shutdown after undeploy. > > (undeployed configuration is still there) > > > > Cheers, > > Simon > > > > >[EMAIL PROTECTED] wrote: > > >This isn't really tied to the console. It is a problem with the > > >deployer itself. If you attempt to undeploy a configuration without > > >first stopping it then the deployer will leave things in this unresolved > > >state. You can avoid the problem by ensuring that you always stop the > > >configuration that you are about to undeploy first. > > >I first noticed this problem in the console deploy/undeploy portlet(s). > > >I provided a fix within the console that ensures that the > > >configuration is stopped before we attempt to undeploy it even if the > > >user didn't explicitly stop it. That is the fix that was integrated > > >over the weekend and so it is now impossible to hit this error if you > > >are using the console deploy/undeploy functions. > > >> > > >>[EMAIL PROTECTED] wrote: > > >> I'm using deployer.jar to do deploy and undeploy; not sure why this bug > > >> is tied to the console > > >> config.xml is not updated correctly on the shutdown (deploy-undeploy > > >> works fine) > > >> > > >> Simon > > > > > > > > > > > >
