You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2004/11/05 05:25:32 UTC
[jira] Created: (GERONIMO-442) Demo module isn't started properly
Demo module isn't started properly
----------------------------------
Key: GERONIMO-442
URL: http://nagoya.apache.org/jira/browse/GERONIMO-442
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:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-442) Demo module isn't started properly
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-442?page=all ]
Aaron Mulder resolved GERONIMO-442:
-----------------------------------
Fix Version: 1.0-M4
Resolution: Fixed
Probably caused because o/a/g/Demo depended on o/a/g/Secure and the latter was not automatically started when the former was. If that's right, it was fixed in 216276.
In any case, the Demo module now starts and shows up as running.
> Demo module isn't started properly
> ----------------------------------
>
> Key: GERONIMO-442
> URL: http://issues.apache.org/jira/browse/GERONIMO-442
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0-M2
> Reporter: Aaron Mulder
> Fix For: 1.0-M4
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-442) Demo module isn't started properly
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-442?page=all ]
Dain Sundstrom closed GERONIMO-442:
-----------------------------------
> Demo module isn't started properly
> ----------------------------------
>
> Key: GERONIMO-442
> URL: http://issues.apache.org/jira/browse/GERONIMO-442
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0-M2
> Reporter: Aaron Mulder
> Fix For: 1.0-M4
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-442) Demo module isn't started properly
Posted by "Jeremy Boynes (JIRA)" <de...@geronimo.apache.org>.
[ http://nagoya.apache.org/jira/browse/GERONIMO-442?page=comments#action_55075 ]
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: http://nagoya.apache.org/jira/browse/GERONIMO-442
> 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:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira