[jira] Updated: (GERONIMO-1451) A new TCP listener for ActiveMQ is not persisting across server startups

["Donald Woods (JIRA)" <de...@geronimo.apache.org>]

     [ http://issues.apache.org/jira/browse/GERONIMO-1451?page=all ]

Donald Woods updated GERONIMO-1451:
-----------------------------------

    Attachment: ActiveMQConnectorGBean.patch
                ActiveMQManagerGBean.patch

Patches from Phani and Vamsi that need to be applied to ActiveMQ.
I verified the patches work with ActiveMQ 3.2.2 and the latest Geronimo branches/1.0 code form late Feb.

>  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
>         Type: Bug
>   Components: ActiveMQ
>     Versions: 1.0
>  Environment: Windows 2003, Sun JVM java version "1.4.2_09"
>     Reporter: Phani Balaji Madgula
>     Assignee: Aaron Mulder
>      Fix For: 1.1, 1.2
>  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