qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-1686) Configuration Update removes ability ot have multiple distinct InVM brokers.
Date Wed, 15 Feb 2012 22:23:59 GMT

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

Robbie Gemmell resolved QPID-1686.

    Resolution: Won't Fix

The ability to use multiple brokers in the same JVM was eventually fully removed, a new feature
JIRA will be raised if this is to be restored in future.
> Configuration Update removes ability ot have multiple distinct InVM brokers.
> ----------------------------------------------------------------------------
>                 Key: QPID-1686
>                 URL: https://issues.apache.org/jira/browse/QPID-1686
>             Project: Qpid
>          Issue Type: Bug
>            Reporter: Martin Ritchie
>            Priority: Minor
> Before the change creating a new ApplicationRegistry with an id would result in a distinct
> Now the code is littered with ApplicationRegistry.getInstance() calls which returns the
AR with id 1.
> This prevents us having InVM brokers with their own config.
> The problem can be removed if the new Configuration objects form a tree so you can do:
> QueueConfig.getVHostConfig().getServerConfig() 
> This could then replace the short cut of using AR.getInstance().

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


Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message