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/05/21 15:55:55 UTC
[jira] Created: (QPID-1086) (01.0 dode path) Client doe not
implement session.flush confirmed
(01.0 dode path) Client doe not implement session.flush confirmed
-----------------------------------------------------------------
Key: QPID-1086
URL: https://issues.apache.org/jira/browse/QPID-1086
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: M3
Reporter: Arnaud Simon
Fix For: M3
The 0.10 c++ broker now sends a session.flush confirmed and completed every 64 Kb the client however does not support session.flush confirmed.
I can think about 3 solutions:
1) do not respond to session.flush confirmed
2) do the same than for session.flush completed
3) implement it
I would suggest that 2) would be a good quick fix that is AMQP compliant. We'll implement 3) later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1086) (01.0 dode path) Client does not
implement session.flush confirmed
Posted by "Arnaud Simon (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Simon updated QPID-1086:
-------------------------------
Summary: (01.0 dode path) Client does not implement session.flush confirmed (was: (01.0 dode path) Client doe not implement session.flush confirmed)
> (01.0 dode path) Client does not implement session.flush confirmed
> ------------------------------------------------------------------
>
> Key: QPID-1086
> URL: https://issues.apache.org/jira/browse/QPID-1086
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M3
> Reporter: Arnaud Simon
> Fix For: M3
>
>
> The 0.10 c++ broker now sends a session.flush confirmed and completed every 64 Kb the client however does not support session.flush confirmed.
> I can think about 3 solutions:
> 1) do not respond to session.flush confirmed
> 2) do the same than for session.flush completed
> 3) implement it
> I would suggest that 2) would be a good quick fix that is AMQP compliant. We'll implement 3) later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-1086) (01.0 dode path) Client doe not
implement session.flush confirmed
Posted by "Arnaud Simon (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Simon resolved QPID-1086.
--------------------------------
Resolution: Fixed
This issue is fixed (checked in solution 2) but we may want to implement solution 3
> (01.0 dode path) Client doe not implement session.flush confirmed
> -----------------------------------------------------------------
>
> Key: QPID-1086
> URL: https://issues.apache.org/jira/browse/QPID-1086
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M3
> Reporter: Arnaud Simon
> Fix For: M3
>
>
> The 0.10 c++ broker now sends a session.flush confirmed and completed every 64 Kb the client however does not support session.flush confirmed.
> I can think about 3 solutions:
> 1) do not respond to session.flush confirmed
> 2) do the same than for session.flush completed
> 3) implement it
> I would suggest that 2) would be a good quick fix that is AMQP compliant. We'll implement 3) later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.