geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Boynes (JIRA)" <>
Subject [jira] Commented: (GERONIMO-442) Demo module isn't started properly
Date Fri, 05 Nov 2004 04:44:32 GMT
     [ ]
Jeremy Boynes commented on GERONIMO-442:

I would guess that the configuration started but some of the GBeans within it are still STARTING
(waiting for dependencies) or have FAILED.

> Demo module isn't started properly
> ----------------------------------
>          Key: GERONIMO-442
>          URL:
>      Project: Apache Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0-M2
>     Reporter: Aaron Mulder

> When you issue a JSR-88 "start" command on module "org/apache/geronimo/Demo", the server
reports that it's starting the configuration, and the ProgressObject returns success and returns
the TargetModuleID for the affected configuration.
> However, org/apache/geronimo/Demo still shows up in the stopped module list.
> It appears to actually be running, though -- if you stop it once it stops, and if you
stop it again it fails with a NoSuchConfigException.  Likewise if you try to start it twice
the second time fails.
> It seems the bug is in how the started/stopped list is generated, though a module such
as org/apache/geronimo/SystemJMS (or o/a/g/DefaultDatabase) can be stopped and started successfully.
 Might be specific to web apps?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message