You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rupert Smith (JIRA)" <qp...@incubator.apache.org> on 2008/01/28 12:51:35 UTC
[jira] Created: (QPID-764) .Net can cause negative reference count
on Java broker.
.Net can cause negative reference count on Java broker.
-------------------------------------------------------
Key: QPID-764
URL: https://issues.apache.org/jira/browse/QPID-764
Project: Qpid
Issue Type: Bug
Components: Dot Net Client, Java Broker
Affects Versions: M2
Reporter: Rupert Smith
Fix For: M2.1
... if channels not closed properly. Added Close() methods to channels/publishers/consumers so that things can be closed down properly. Lack of closing meant that multiple acks are being send.
However, reference counting is internal to the broker, and should not go negative even if clients misbehave, so creating this JIRA for resolution against the JAva broker. Test case to follow...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-764) .Net can cause negative reference
count on Java broker.
Posted by "Rupert Smith (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563130#action_12563130 ]
Rupert Smith commented on QPID-764:
-----------------------------------
Don't seem to be able to reproduce the issue, and I checked out older versions of the .Net too to try out the tests where the clean-up was not properly done. Will have to assume that there is no issue on M2 or M2.1 at the moment.
> .Net can cause negative reference count on Java broker.
> -------------------------------------------------------
>
> Key: QPID-764
> URL: https://issues.apache.org/jira/browse/QPID-764
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client, Java Broker
> Affects Versions: M2
> Reporter: Rupert Smith
> Fix For: M2.1
>
>
> ... if channels not closed properly. Added Close() methods to channels/publishers/consumers so that things can be closed down properly. Lack of closing meant that multiple acks are being send.
> However, reference counting is internal to the broker, and should not go negative even if clients misbehave, so creating this JIRA for resolution against the JAva broker. Test case to follow...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-764) .Net can cause negative reference count
on Java broker.
Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey resolved QPID-764.
------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: M2.1)
Could not reproduce, so closing
> .Net can cause negative reference count on Java broker.
> -------------------------------------------------------
>
> Key: QPID-764
> URL: https://issues.apache.org/jira/browse/QPID-764
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client, Java Broker
> Affects Versions: M2
> Reporter: Rupert Smith
>
> ... if channels not closed properly. Added Close() methods to channels/publishers/consumers so that things can be closed down properly. Lack of closing meant that multiple acks are being send.
> However, reference counting is internal to the broker, and should not go negative even if clients misbehave, so creating this JIRA for resolution against the JAva broker. Test case to follow...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.