You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrew Kennedy (JIRA)" <ji...@apache.org> on 2011/01/31 18:11:29 UTC

[jira] Created: (QPID-3026) The ApplicationRegistry object should be a singleton

The ApplicationRegistry object should be a singleton
----------------------------------------------------

                 Key: QPID-3026
                 URL: https://issues.apache.org/jira/browse/QPID-3026
             Project: Qpid
          Issue Type: Improvement
          Components: Java Broker
    Affects Versions: 0.9
            Reporter: Andrew Kennedy
            Assignee: Andrew Kennedy
            Priority: Minor


The ApplicationRegistry can currently have multiple instances, in order to cater for multiple brokers in the same VM. However, *many* parts of the code simply call ApplcationRegistry.getInstance() to obtain a reference, meaning multiple instances are ignored. The only time this is ever useful is for certain types of tests, therefore the capability to have multiple broker instances should be removed.

Any tests that require multiple brokers can start a VM broker and an external, or two external brokers. In general, test-only code should not be made available to the rest of the application.

-- 
This message is automatically generated by JIRA.
-
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


[jira] [Commented] (QPID-3026) The ApplicationRegistry object should be a singleton

Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061370#comment-13061370 ] 

Robbie Gemmell commented on QPID-3026:
--------------------------------------

Keith and I have been working on this together as discussed on the mailing list previously. It is being attached here to grant the appropriate permissions for inclusion.

> The ApplicationRegistry object should be a singleton
> ----------------------------------------------------
>
>                 Key: QPID-3026
>                 URL: https://issues.apache.org/jira/browse/QPID-3026
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: 0.9
>            Reporter: Andrew Kennedy
>            Assignee: Robbie Gemmell
>            Priority: Minor
>             Fix For: 0.11
>
>         Attachments: 0005-QPID-3026-remove-incomplete-support-for-multiple-App.patch
>
>
> The ApplicationRegistry can currently have multiple instances, in order to cater for multiple brokers in the same VM. However, *many* parts of the code simply call ApplcationRegistry.getInstance() to obtain a reference, meaning multiple instances are ignored. The only time this is ever useful is for certain types of tests, therefore the capability to have multiple broker instances should be removed.
> Any tests that require multiple brokers can start a VM broker and an external, or two external brokers. In general, test-only code should not be made available to the rest of the application.

--
This message is automatically generated by JIRA.
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


[jira] [Resolved] (QPID-3026) The ApplicationRegistry object should be a singleton

Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell resolved QPID-3026.
----------------------------------

    Resolution: Fixed

Closing out, patch applied.

> The ApplicationRegistry object should be a singleton
> ----------------------------------------------------
>
>                 Key: QPID-3026
>                 URL: https://issues.apache.org/jira/browse/QPID-3026
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: 0.9
>            Reporter: Andrew Kennedy
>            Assignee: Robbie Gemmell
>            Priority: Minor
>             Fix For: 0.11
>
>         Attachments: 0005-QPID-3026-remove-incomplete-support-for-multiple-App.patch
>
>
> The ApplicationRegistry can currently have multiple instances, in order to cater for multiple brokers in the same VM. However, *many* parts of the code simply call ApplcationRegistry.getInstance() to obtain a reference, meaning multiple instances are ignored. The only time this is ever useful is for certain types of tests, therefore the capability to have multiple broker instances should be removed.
> Any tests that require multiple brokers can start a VM broker and an external, or two external brokers. In general, test-only code should not be made available to the rest of the application.

--
This message is automatically generated by JIRA.
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


[jira] Updated: (QPID-3026) The ApplicationRegistry object should be a singleton

Posted by "Andrew Kennedy (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kennedy updated QPID-3026:
---------------------------------

    Fix Version/s: 0.11

> The ApplicationRegistry object should be a singleton
> ----------------------------------------------------
>
>                 Key: QPID-3026
>                 URL: https://issues.apache.org/jira/browse/QPID-3026
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: 0.9
>            Reporter: Andrew Kennedy
>            Assignee: Andrew Kennedy
>            Priority: Minor
>             Fix For: 0.11
>
>
> The ApplicationRegistry can currently have multiple instances, in order to cater for multiple brokers in the same VM. However, *many* parts of the code simply call ApplcationRegistry.getInstance() to obtain a reference, meaning multiple instances are ignored. The only time this is ever useful is for certain types of tests, therefore the capability to have multiple broker instances should be removed.
> Any tests that require multiple brokers can start a VM broker and an external, or two external brokers. In general, test-only code should not be made available to the rest of the application.

--
This message is automatically generated by JIRA.
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


[jira] [Assigned] (QPID-3026) The ApplicationRegistry object should be a singleton

Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall reassigned QPID-3026:
--------------------------------

    Assignee: Keith Wall  (was: Andrew Kennedy)

> The ApplicationRegistry object should be a singleton
> ----------------------------------------------------
>
>                 Key: QPID-3026
>                 URL: https://issues.apache.org/jira/browse/QPID-3026
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: 0.9
>            Reporter: Andrew Kennedy
>            Assignee: Keith Wall
>            Priority: Minor
>             Fix For: 0.11
>
>
> The ApplicationRegistry can currently have multiple instances, in order to cater for multiple brokers in the same VM. However, *many* parts of the code simply call ApplcationRegistry.getInstance() to obtain a reference, meaning multiple instances are ignored. The only time this is ever useful is for certain types of tests, therefore the capability to have multiple broker instances should be removed.
> Any tests that require multiple brokers can start a VM broker and an external, or two external brokers. In general, test-only code should not be made available to the rest of the application.

--
This message is automatically generated by JIRA.
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


[jira] [Updated] (QPID-3026) The ApplicationRegistry object should be a singleton

Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall updated QPID-3026:
-----------------------------

    Attachment: 0005-QPID-3026-remove-incomplete-support-for-multiple-App.patch

Patch to complete this improvement.

> The ApplicationRegistry object should be a singleton
> ----------------------------------------------------
>
>                 Key: QPID-3026
>                 URL: https://issues.apache.org/jira/browse/QPID-3026
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: 0.9
>            Reporter: Andrew Kennedy
>            Assignee: Keith Wall
>            Priority: Minor
>             Fix For: 0.11
>
>         Attachments: 0005-QPID-3026-remove-incomplete-support-for-multiple-App.patch
>
>
> The ApplicationRegistry can currently have multiple instances, in order to cater for multiple brokers in the same VM. However, *many* parts of the code simply call ApplcationRegistry.getInstance() to obtain a reference, meaning multiple instances are ignored. The only time this is ever useful is for certain types of tests, therefore the capability to have multiple broker instances should be removed.
> Any tests that require multiple brokers can start a VM broker and an external, or two external brokers. In general, test-only code should not be made available to the rest of the application.

--
This message is automatically generated by JIRA.
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


[jira] [Assigned] (QPID-3026) The ApplicationRegistry object should be a singleton

Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall reassigned QPID-3026:
--------------------------------

    Assignee: Robbie Gemmell  (was: Keith Wall)

> The ApplicationRegistry object should be a singleton
> ----------------------------------------------------
>
>                 Key: QPID-3026
>                 URL: https://issues.apache.org/jira/browse/QPID-3026
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: 0.9
>            Reporter: Andrew Kennedy
>            Assignee: Robbie Gemmell
>            Priority: Minor
>             Fix For: 0.11
>
>         Attachments: 0005-QPID-3026-remove-incomplete-support-for-multiple-App.patch
>
>
> The ApplicationRegistry can currently have multiple instances, in order to cater for multiple brokers in the same VM. However, *many* parts of the code simply call ApplcationRegistry.getInstance() to obtain a reference, meaning multiple instances are ignored. The only time this is ever useful is for certain types of tests, therefore the capability to have multiple broker instances should be removed.
> Any tests that require multiple brokers can start a VM broker and an external, or two external brokers. In general, test-only code should not be made available to the rest of the application.

--
This message is automatically generated by JIRA.
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