[ http://issues.apache.org/jira/browse/GERONIMO-2423?page=comments#action_12436910 ] David Jencks commented on GERONIMO-2423: ----------------------------------------
I'm not clear on what Heinz is doing or if it is the same as GERONIMO-2341. If you are editing the console.xml by hand when the server is stopped, you need to add the attribute load="false" to the gbean entry that you want to supress. Deleting the gbean entry means "don't change what is specified in the car file for this gbean", in other words start the gbean. If you are using the console to stop the connector this sounds like the same problem as 2341. > Unable to delete TomcatAJPConnector > ----------------------------------- > > Key: GERONIMO-2423 > URL: http://issues.apache.org/jira/browse/GERONIMO-2423 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console > Affects Versions: 1.1.1 > Environment: Linux, Windows > Reporter: Heinz Drews > > Even after deleting the default TomcatAJPConnector it is activated again > after server restart. > Next attempt to delete the connector results in message [TomcatManagerImpl] > No such GBean > 'geronimo/tomcat/1.1.1/car?ServiceModule=geronimo/tomcat/1.1.1/car,j2eeType=GBean,name=TomcatAJPConnector' -- 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
