You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <qp...@incubator.apache.org> on 2008/04/28 12:00:55 UTC

[jira] Created: (QPID-974) Need to allow the size of the queue of outgoing frames to be limited

Need to allow the size of the queue of outgoing frames to be limited
--------------------------------------------------------------------

                 Key: QPID-974
                 URL: https://issues.apache.org/jira/browse/QPID-974
             Project: Qpid
          Issue Type: Improvement
          Components: C++ Client
    Affects Versions: M3
            Reporter: Gordon Sim
            Assignee: Gordon Sim
             Fix For: M3


The c++ client has a separate IO thread that actually writes frames to the socket. The application thread merely queues up the frames created for the commands/messages it sends. Without some form of bounds on this queue of frames, the client continues to consume memory.

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


[jira] Closed: (QPID-974) Need to allow the size of the queue of outgoing frames to be limited

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

Gordon Sim closed QPID-974.
---------------------------


> Need to allow the size of the queue of outgoing frames to be limited
> --------------------------------------------------------------------
>
>                 Key: QPID-974
>                 URL: https://issues.apache.org/jira/browse/QPID-974
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Client
>    Affects Versions: M3
>            Reporter: Gordon Sim
>            Assignee: Gordon Sim
>             Fix For: M3
>
>
> The c++ client has a separate IO thread that actually writes frames to the socket. The application thread merely queues up the frames created for the commands/messages it sends. Without some form of bounds on this queue of frames, the client continues to consume memory.

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


[jira] Resolved: (QPID-974) Need to allow the size of the queue of outgoing frames to be limited

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

Gordon Sim resolved QPID-974.
-----------------------------

    Resolution: Fixed

Clients queue of outgoing messages may now be bounded by setting it to a multiple of the buffer size (i.e max frame size). The default is 2.

> Need to allow the size of the queue of outgoing frames to be limited
> --------------------------------------------------------------------
>
>                 Key: QPID-974
>                 URL: https://issues.apache.org/jira/browse/QPID-974
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Client
>    Affects Versions: M3
>            Reporter: Gordon Sim
>            Assignee: Gordon Sim
>             Fix For: M3
>
>
> The c++ client has a separate IO thread that actually writes frames to the socket. The application thread merely queues up the frames created for the commands/messages it sends. Without some form of bounds on this queue of frames, the client continues to consume memory.

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