geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1451) A new TCP listener for ActiveMQ is not persisting across server startups
Date Tue, 06 Jun 2006 20:55:30 GMT
    [ ] 

Hiram Chirino commented on GERONIMO-1451:

I looks like the 2nd patch: ActiveMQManagerGBean.patch  might not be right.. it's against
the module gbean... are you sure that you don't want to patch the gbean-g1_1 module instead?
 the gbean is being left for geronimo 1.0.x compatibility, and the gbean-g1_1 is for the new
1.1.x branch.

>  A new TCP listener for ActiveMQ is not persisting across server startups
> -------------------------------------------------------------------------
>          Key: GERONIMO-1451
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: ActiveMQ
>     Versions: 1.0
>  Environment: Windows 2003, Sun JVM java version "1.4.2_09"
>     Reporter: Phani Balaji Madgula
>     Assignee: Aaron Mulder
>     Priority: Critical
>      Fix For: 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:
For more information on JIRA, see:

View raw message