You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Phani Madgula <ph...@gmail.com> on 2006/01/11 11:21:06 UTC
A new TCP listener for ActiveMQ is not shown across server startups
Hi
I am facing a problem while creating a new TCP listener for ActiveMQ through
console.
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 restart the server, the listener is not shown in "JMS
Network Listeners" portlet.
The problem is that, I guess, when we create a new HTTP listener for
Tomcat, the details are persisted into config.xml.
But, when creating a new ActiveMQ TCP listener, the details are not
persisted into config.xml
How can I accomplish the above task?
Thanks
phani
Re: A new TCP listener for ActiveMQ is not shown across server startups
Posted by Vamsavardhana Reddy <c1...@gmail.com>.
Phani,
This issue is similar to JIRA issue GERONIMO-1070. To fix this,
ActiveMQManagerGBean class should use EditableConfigurationManager to
add/remove connectors so that the changes are not lost upon stopping the
server. I suggest to report this problem in Geronimo JIRA.
-Vamsi
On 1/11/06, Phani Madgula <ph...@gmail.com> wrote:
>
> Hi
> I am facing a problem while creating a new TCP listener for ActiveMQ
> through console.
>
> 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 restart the server, the listener is not shown in "JMS
> Network Listeners" portlet.
>
> The problem is that, I guess, when we create a new HTTP listener for
> Tomcat, the details are persisted into config.xml.
> But, when creating a new ActiveMQ TCP listener, the details are not
> persisted into config.xml
>
> How can I accomplish the above task?
>
> Thanks
> phani
>
Re: A new TCP listener for ActiveMQ is not shown across server startups
Posted by Vamsavardhana Reddy <c1...@gmail.com>.
Phani,
This issue is similar to JIRA issue GERONIMO-1070. To fix this,
ActiveMQManagerGBean class should use EditableConfigurationManager to
add/remove connectors so that the changes are not lost upon stopping the
server. I suggest to report this problem in Geronimo JIRA.
-Vamsi
On 1/11/06, Phani Madgula <ph...@gmail.com> wrote:
>
> Hi
> I am facing a problem while creating a new TCP listener for ActiveMQ
> through console.
>
> 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 restart the server, the listener is not shown in "JMS
> Network Listeners" portlet.
>
> The problem is that, I guess, when we create a new HTTP listener for
> Tomcat, the details are persisted into config.xml.
> But, when creating a new ActiveMQ TCP listener, the details are not
> persisted into config.xml
>
> How can I accomplish the above task?
>
> Thanks
> phani
>