[ http://issues.apache.org/jira/browse/GERONIMO-1451?page=comments#action_12422449 ] Vamsavardhana Reddy commented on GERONIMO-1451: -----------------------------------------------
I have verified the behaviour in Geronimo jetty server built from tags/1.1.0 . The issue seems to have been resolved. Perhaps the first patch got applied as part of GERONIMO-1906 . I do not know what changes accounted for the second patch. > A new TCP listener for ActiveMQ is not persisting across server startups > ------------------------------------------------------------------------- > > Key: GERONIMO-1451 > URL: http://issues.apache.org/jira/browse/GERONIMO-1451 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ > Affects Versions: 1.1 > Environment: Windows 2003, Sun JVM java version "1.4.2_09" > Reporter: Phani Balaji Madgula > Assigned To: Matt Hogstrom > Priority: Critical > Fix For: 1.1.1 > > Attachments: ActiveMQConnectorGBean.patch, ActiveMQManagerGBean.patch > > > When we click on "Add new tcp listener" on "JMS Network Listeners" portlet, > console asks for details of listener and when submitted with proper values, > it creates a TCP listener and starts it. > But, when we shutdown and restart the server, the listener is not shown in > "JMS Network Listeners" portlet. > The problem is that, I guess, the GBean pertaining to the new TCP listener is > not saved to config.xml. But the same functionality is working fine for > tomcat HTTP listeners. > This problem is similar to GERONIMO-1070. -- 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
