qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Ritchie" <ritch...@apache.org>
Subject Re: [jira] Resolved: (QPID-7) Occasionally messages are ack'd more than once
Date Fri, 29 Sep 2006 09:57:52 GMT
There is a comment on the JIRA with a description of what the
resolution was. Do you want more details?

Martin Ritchie [27/Sep/06 04:40 AM]
Revision 450401.

While the data was being put in tot the unack'd map correctly the sync
block did not include the writeFrame call hence the messages could be
sent to client out of order.

This revision should finally resolve this issue.


On 29/09/06, John O'Hara <john.r.ohara@gmail.com> wrote:
> Can you add a wee note saying roughly how it was fixed?
>
> On 29/09/06, Martin Ritchie (JIRA) <qpid-dev@incubator.apache.org> wrote:
> >
> >      [ http://issues.apache.org/jira/browse/QPID-7?page=all ]
> >
> > Martin Ritchie resolved QPID-7.
> > -------------------------------
> >
> >     Resolution: Fixed
> >
> > See other comments
> >
> > > Occasionally messages are ack'd more than once
> > > ----------------------------------------------
> > >
> > >                 Key: QPID-7
> > >                 URL: http://issues.apache.org/jira/browse/QPID-7
> > >             Project: Qpid
> > >          Issue Type: Bug
> > >          Components: Java Broker
> > >            Reporter: Martin Ritchie
> > >         Assigned To: Martin Ritchie
> > >
> > > When running a single queue and sending and receiving to that queue in
> > the same session (Not in a transaction) occasionally the broker appears to
> > get multiple acks for a given tag. Interestingly when running inside a
> > transaction this doesn't happen.
> > > 2006-09-21 10:35:24,763 ERROR [pool-10-thread-4] state.AMQStateManager (
> > AMQStateManager.java:150) - State manager received error notification:
> > org.apache.qpid.AMQException: Single ack on delivery tag 434 not known for
> > channel:1
> > > org.apache.qpid.AMQException: Single ack on delivery tag 434 not known
> > for channel:1
> > >       at org.apache.qpid.server.AMQChannel.handleAcknowledgement(
> > AMQChannel.java:550)
> > >       at org.apache.qpid.server.AMQChannel.acknowledgeMessage(
> > AMQChannel.java:492)
> > >       at
> > org.apache.qpid.server.handler.BasicAckMethodHandler.methodReceived(
> > BasicAckMethodHandler.java:50)
> > >       at org.apache.qpid.server.state.AMQStateManager.methodReceived(
> > AMQStateManager.java:165)
> > >       at
> > org.apache.qpid.server.protocol.AMQMinaProtocolSession.methodFrameReceived
> > (AMQMinaProtocolSession.java:358)
> > >       at
> > org.apache.qpid.server.protocol.AMQMinaProtocolSession.dataBlockReceived(
> > AMQMinaProtocolSession.java:326)
> > >       at
> > org.apache.qpid.server.protocol.AMQPFastProtocolHandler.messageReceived(
> > AMQPFastProtocolHandler.java:181)
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > If you think it was sent incorrectly contact one of the administrators:
> > http://issues.apache.org/jira/secure/Administrators.jspa
> > -
> > For more information on JIRA, see: http://www.atlassian.com/software/jira
> >
> >
> >
>
>


-- 
Martin Ritchie

Mime
View raw message