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/06/13 18:23:26 UTC
[jira] Created: (QPID-508) [Memory Leak] Broker does not return
mandatory messages sent outside of a transaction.
[Memory Leak] Broker does not return mandatory messages sent outside of a transaction.
--------------------------------------------------------------------------------------
Key: QPID-508
URL: https://issues.apache.org/jira/browse/QPID-508
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: M1, M2
Reporter: Martin Ritchie
Assignee: Martin Ritchie
Currently message are placed into _returnMessage but these messages are only processed by the TxCommit Handler. So this queue just grow till OOME for non-transactional messaging.
Problem with the broker is masked for the queue case by the client as it does a Non-AMQ check to see if the queue is bound. Which is part of the JMS Spec. The JMS Spec doesn't call for checking that a given topic has a valid routing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (QPID-508) [Memory Leak] Broker does not return
mandatory messages sent outside of a transaction.
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-508:
-----------------------------------
Assignee: Martin Ritchie
> [Memory Leak] Broker does not return mandatory messages sent outside of a transaction.
> --------------------------------------------------------------------------------------
>
> Key: QPID-508
> URL: https://issues.apache.org/jira/browse/QPID-508
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M2
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M2
>
>
> Currently message are placed into _returnMessage but these messages are only processed by the TxCommit Handler. So this queue just grow till OOME for non-transactional messaging.
> Problem with the broker is masked for the queue case by the client as it does a Non-AMQ check to see if the queue is bound. Which is part of the JMS Spec. The JMS Spec doesn't call for checking that a given topic has a valid routing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-508) [Memory Leak] Broker does not return
mandatory messages sent outside of a transaction.
Posted by "Rupert Smith (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Smith resolved QPID-508.
-------------------------------
Resolution: Fixed
The post commit handling is now called.
There was a problem with headers only messages not being cleaned up, because the clean-up call was only being made after body was received. This is fixed too.
Mandatory and Immediate messages are now both returned when appropriate.
> [Memory Leak] Broker does not return mandatory messages sent outside of a transaction.
> --------------------------------------------------------------------------------------
>
> Key: QPID-508
> URL: https://issues.apache.org/jira/browse/QPID-508
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M2
> Reporter: Martin Ritchie
> Fix For: M2
>
>
> Currently message are placed into _returnMessage but these messages are only processed by the TxCommit Handler. So this queue just grow till OOME for non-transactional messaging.
> Problem with the broker is masked for the queue case by the client as it does a Non-AMQ check to see if the queue is bound. Which is part of the JMS Spec. The JMS Spec doesn't call for checking that a given topic has a valid routing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (QPID-508) [Memory Leak] Broker does not return
mandatory messages sent outside of a transaction.
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-508:
-----------------------------------
Assignee: (was: Martin Ritchie)
> [Memory Leak] Broker does not return mandatory messages sent outside of a transaction.
> --------------------------------------------------------------------------------------
>
> Key: QPID-508
> URL: https://issues.apache.org/jira/browse/QPID-508
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M2
> Reporter: Martin Ritchie
> Fix For: M2
>
>
> Currently message are placed into _returnMessage but these messages are only processed by the TxCommit Handler. So this queue just grow till OOME for non-transactional messaging.
> Problem with the broker is masked for the queue case by the client as it does a Non-AMQ check to see if the queue is bound. Which is part of the JMS Spec. The JMS Spec doesn't call for checking that a given topic has a valid routing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-508) [Memory Leak] Broker does not return
mandatory messages sent outside of a transaction.
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-508:
--------------------------------
Fix Version/s: M2
Affects Version/s: (was: M1)
> [Memory Leak] Broker does not return mandatory messages sent outside of a transaction.
> --------------------------------------------------------------------------------------
>
> Key: QPID-508
> URL: https://issues.apache.org/jira/browse/QPID-508
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M2
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M2
>
>
> Currently message are placed into _returnMessage but these messages are only processed by the TxCommit Handler. So this queue just grow till OOME for non-transactional messaging.
> Problem with the broker is masked for the queue case by the client as it does a Non-AMQ check to see if the queue is bound. Which is part of the JMS Spec. The JMS Spec doesn't call for checking that a given topic has a valid routing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.