geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Hogstrom (JIRA)" <>
Subject [jira] Closed: (GERONIMO-1451) A new TCP listener for ActiveMQ is not persisting across server startups
Date Mon, 24 Jul 2006 14:19:14 GMT
     [ ]

Matt Hogstrom closed GERONIMO-1451.

    Fix Version/s: 1.0
                       (was: 1.1.1)
       Resolution: Fixed

According to Vamsavardhana Reddy's e-mail on 7/20 this issue seems to be resolved.  If this
is not correct please reopen with comments.

>  A new TCP listener for ActiveMQ is not persisting across server startups
> -------------------------------------------------------------------------
>                 Key: GERONIMO-1451
>                 URL:
>             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
>            Priority: Critical
>             Fix For: 1.0
>         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:
For more information on JIRA, see:


View raw message