activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3526) JDBC persistence adapter, destination mbeans not visible on restart till producers or consumers reattach
Date Fri, 07 Oct 2011 11:04:29 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully resolved AMQ-3526.
-----------------------------

    Resolution: Fixed

fix and test in  http://svn.apache.org/viewvc?rev=1179999&view=rev
                
> JDBC persistence adapter, destination mbeans not visible on restart till producers or
consumers  reattach
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3526
>                 URL: https://issues.apache.org/jira/browse/AMQ-3526
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMX
>    Affects Versions: 5.5.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: destinations, jdbc, jmx, restart
>             Fix For: 5.6.0
>
>
> With the jdbc store, if there are pending messages on a restart, the destinations do
not appear in jmx till they are reused. So inactive destinations are not recreated on restart.
> Any use of the destination will get the mbean to be created, new producer/consumer etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message