You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/10/11 14:51:50 UTC

[jira] Created: (QPID-636) When populating the PDQ it is possible to throw a NPE

When populating the PDQ it is possible to throw a NPE
-----------------------------------------------------

                 Key: QPID-636
                 URL: https://issues.apache.org/jira/browse/QPID-636
             Project: Qpid
          Issue Type: Bug
    Affects Versions: M2
            Reporter: Martin Ritchie
            Assignee: Martin Ritchie
             Fix For: M2, M2.1, M3


if a message exists on the _messages queue that has actually been delivered to a consumer then there is a chance the meta data has been purged so a NPE will occur on looking up the MetaData. 

We should simply check to see if the message has been delivered if it has then there is no point putting it in the PDQ.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (QPID-636) When populating the PDQ it is possible to throw a NPE

Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aidan Skinner updated QPID-636:
-------------------------------

    Component/s:     (was: C++ Broker)
                 Java Broker

> When populating the PDQ it is possible to throw a NPE
> -----------------------------------------------------
>
>                 Key: QPID-636
>                 URL: https://issues.apache.org/jira/browse/QPID-636
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M2, M2.1
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>             Fix For: M3
>
>
> if a message exists on the _messages queue that has actually been delivered to a consumer then there is a chance the meta data has been purged so a NPE will occur on looking up the MetaData. 
> We should simply check to see if the message has been delivered if it has then there is no point putting it in the PDQ.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (QPID-636) When populating the PDQ it is possible to throw a NPE

Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aidan Skinner updated QPID-636:
-------------------------------

          Component/s: C++ Broker
    Affects Version/s: M2.1

> When populating the PDQ it is possible to throw a NPE
> -----------------------------------------------------
>
>                 Key: QPID-636
>                 URL: https://issues.apache.org/jira/browse/QPID-636
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M2, M2.1
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>             Fix For: M3
>
>
> if a message exists on the _messages queue that has actually been delivered to a consumer then there is a chance the meta data has been purged so a NPE will occur on looking up the MetaData. 
> We should simply check to see if the message has been delivered if it has then there is no point putting it in the PDQ.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (QPID-636) When populating the PDQ it is possible to throw a NPE

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie updated QPID-636:
--------------------------------

    Fix Version/s:     (was: M2.1)
                       (was: M2)

> When populating the PDQ it is possible to throw a NPE
> -----------------------------------------------------
>
>                 Key: QPID-636
>                 URL: https://issues.apache.org/jira/browse/QPID-636
>             Project: Qpid
>          Issue Type: Bug
>    Affects Versions: M2
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>             Fix For: M3
>
>
> if a message exists on the _messages queue that has actually been delivered to a consumer then there is a chance the meta data has been purged so a NPE will occur on looking up the MetaData. 
> We should simply check to see if the message has been delivered if it has then there is no point putting it in the PDQ.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (QPID-636) When populating the PDQ it is possible to throw a NPE

Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aidan Skinner closed QPID-636.
------------------------------

    Resolution: Fixed

This has been fixed by the removal of CSDM

> When populating the PDQ it is possible to throw a NPE
> -----------------------------------------------------
>
>                 Key: QPID-636
>                 URL: https://issues.apache.org/jira/browse/QPID-636
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M2, M2.1
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>             Fix For: M3
>
>
> if a message exists on the _messages queue that has actually been delivered to a consumer then there is a chance the meta data has been purged so a NPE will occur on looking up the MetaData. 
> We should simply check to see if the message has been delivered if it has then there is no point putting it in the PDQ.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.