Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <1202923916.1136985320955.JavaMail.jira@ajax.apache.org>
Date: Wed, 11 Jan 2006 14:15:20 +0100 (CET)
From: "Vamsavardhana Reddy (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-1451)  A new TCP listener for ActiveMQ
 is not persisting across server startups
In-Reply-To: <1501178048.1136983880309.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Vamsavardhana Reddy commented on GERONIMO-1451:
-----------------------------------------------

To fix this, ActiveMQManagerGBean class should use EditableConfigurationManager to add/remove connectors so that the changes are not lost upon stopping the server.  ActiveMQManagerGBean.java is not in Geronimo source tree.

>  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

>
> 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