[ http://issues.apache.org/jira/browse/GERONIMO-2058?page=all ]
David Jencks closed GERONIMO-2058:
----------------------------------
Resolution: Fixed
Fixed in trunk (1.2) rev 410985 and 1.1 rev 411001. Note that this exposed
another gbean in the jetty config.xmls that didn't exist.
> Invalid gbean names in config.xml do not prevent server starting or module
> starting
> -----------------------------------------------------------------------------------
>
> Key: GERONIMO-2058
> URL: http://issues.apache.org/jira/browse/GERONIMO-2058
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: startup/shutdown
> Versions: 1.2, 1.1
> Reporter: David Jencks
> Assignee: David Jencks
> Priority: Blocker
> Fix For: 1.2, 1.1
>
> config.xml has this in it, which includes an invalid gbean name:
> <module name="geronimo/j2ee-security/${pom.currentVersion}/car">
> <gbean name="geronimo.remoting:target=JaasLoginServiceRemotingServer">
> <attribute name="host">${PlanServerHostname}</attribute>
> <attribute name="port">${PlanRemoteLoginPort}</attribute>
> </gbean>
> <gbean name="JMXService">
> <attribute name="protocol">rmi</attribute>
> <attribute name="host">${PlanServerHostname}</attribute>
> <attribute name="port">${PlanJMXPort}</attribute>
> <attribute
> name="urlPath">/jndi/rmi://${PlanServerHostname}:${PlanNamingPort}/JMXConnector</attribute>
> </gbean>
> </module>
> At the minimum this modules shouldn't start: I would prefer the server to not
> start.
> Obviously we also need to fix the name in all the config.xmls, in this case
> it should be name="JaasLoginServiceRemotingServer"
--
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
