You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Arnaud Simon (JIRA)" <qp...@incubator.apache.org> on 2008/06/02 13:09:45 UTC
[jira] Created: (QPID-1109) Decide of Protect io default settings
Decide of Protect io default settings
-------------------------------------
Key: QPID-1109
URL: https://issues.apache.org/jira/browse/QPID-1109
Project: Qpid
Issue Type: Improvement
Components: Java Client
Affects Versions: M3
Reporter: Arnaud Simon
Priority: Minor
Fix For: M3
The current client lib may run out of memory as messages may be queued up faster than they can be written to the wire The protect io layer solves this issue by using a bounded queue that blocks messages producers when the queue is full.
The protect io layer is currently optional, it could be a goo idea to use it as defualt providing that
- it does not degrade performances (I believe it is unlikely to degrade the producer to consumer rate)
- it is fully tested
- the optimum queue size has been determined
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-1109) Decide of Protect io default settings
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-1109.
---------------------------------
Resolution: Fixed
new 0-10 transport layer takes care of this
> Decide of Protect io default settings
> -------------------------------------
>
> Key: QPID-1109
> URL: https://issues.apache.org/jira/browse/QPID-1109
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M3
> Reporter: Arnaud Simon
> Priority: Minor
> Fix For: M3
>
>
> The current client lib may run out of memory as messages may be queued up faster than they can be written to the wire The protect io layer solves this issue by using a bounded queue that blocks messages producers when the queue is full.
> The protect io layer is currently optional, it could be a goo idea to use it as defualt providing that
> - it does not degrade performances (I believe it is unlikely to degrade the producer to consumer rate)
> - it is fully tested
> - the optimum queue size has been determined
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (QPID-1109) Decide of Protect io default settings
Posted by "Arnaud Simon (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Simon closed QPID-1109.
------------------------------
switch to io transport
> Decide of Protect io default settings
> -------------------------------------
>
> Key: QPID-1109
> URL: https://issues.apache.org/jira/browse/QPID-1109
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M3
> Reporter: Arnaud Simon
> Priority: Minor
> Fix For: M3
>
>
> The current client lib may run out of memory as messages may be queued up faster than they can be written to the wire The protect io layer solves this issue by using a bounded queue that blocks messages producers when the queue is full.
> The protect io layer is currently optional, it could be a goo idea to use it as defualt providing that
> - it does not degrade performances (I believe it is unlikely to degrade the producer to consumer rate)
> - it is fully tested
> - the optimum queue size has been determined
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.