[
https://issues.apache.org/jira/browse/QPID-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625691#action_12625691
]
Martin Ritchie commented on QPID-1262:
--------------------------------------
main 2008-08-26 11:17:56,241 DEBUG [qpid.protocol] SEND: [EMAIL PROTECTED]
Frame channelId: 1, bodyFrame: [TxCommitBodyImpl: ]
main 2008-08-26 11:17:56,241 DEBUG [qpid.client.protocol.AMQProtocolHandler]
Blocking for:1000:org.apache.qpid.framing.TxCommitOkBody
pool-2-thread-2 2008-08-26 11:17:56,242 DEBUG
[qpid.server.protocol.AMQProtocolSession] Frame Received: Frame channelId: 1,
bodyFrame: [EMAIL PROTECTED]
pool-2-thread-2 2008-08-26 11:17:56,242 DEBUG [apache.qpid.server.AMQChannel]
Content header received on channel 1
pool-2-thread-2 2008-08-26 11:17:56,243 DEBUG
[qpid.server.exchange.DirectExchange] Publishing message to queue [EMAIL
PROTECTED]
pool-2-thread-2 2008-08-26 11:17:56,244 DEBUG
[qpid.server.txn.LocalTransactionalContext] Starting transaction on message
store: [EMAIL PROTECTED]
pool-2-thread-2 2008-08-26 11:17:56,244 DEBUG
[qpid.server.protocol.AMQProtocolSession] Frame Received: Frame channelId: 1,
bodyFrame: [EMAIL PROTECTED]
pool-2-thread-2 2008-08-26 11:17:56,245 DEBUG [apache.qpid.server.AMQChannel]
1(12838955)Content body received on channel 1
pool-2-thread-2 2008-08-26 11:17:56,246 DEBUG
[qpid.server.queue.IncomingMessage] Delivering message 1 to [EMAIL PROTECTED]
pool-2-thread-2 2008-08-26 11:17:56,249 DEBUG
[qpid.server.protocol.AMQProtocolSession] Frame Received: Frame channelId: 1,
bodyFrame: [TxCommitBodyImpl: ]
pool-2-thread-2 2008-08-26 11:17:56,249 DEBUG
[qpid.server.handler.TxCommitHandler] Commit received on channel 1
pool-2-thread-2 2008-08-26 11:17:56,249 DEBUG
[qpid.server.txn.LocalTransactionalContext] Committing transactional context:
[EMAIL PROTECTED]
pool-2-thread-2 2008-08-26 11:17:56,250 DEBUG [qpid.server.txn.TxnBuffer]
Committing 1 ops to commit.:[EMAIL PROTECTED]
main 2008-08-26 11:17:57,245 DEBUG
[test.client.timeouts.SyncWaitTimeoutDelayTest] Sleeping in session
main 2008-08-26 11:17:58,247 DEBUG
[test.client.timeouts.SyncWaitTimeoutDelayTest] Done Sleep in session
main 2008-08-26 11:17:58,248 WARN
[test.client.timeouts.SyncWaitTimeoutDelayTest] START
main 2008-08-26 11:17:58,248 DEBUG [apache.qpid.framing.AMQDataBlockEncoder]
Encoded frame byte-buffer is
'0x0100010000001d0028000a00000a616d712e646972656374066469726563741000000000ce'
main 2008-08-26 11:17:58,249 DEBUG [qpid.protocol] SEND: [EMAIL PROTECTED]
Frame channelId: 1, bodyFrame: [ExchangeDeclareBodyImpl: ticket=0,
exchange=amq.direct, type=direct, passive=false, durable=false,
autoDelete=false, internal=false, nowait=true, arguments=null]
main 2008-08-26 11:17:58,249 DEBUG
[apache.qpid.client.BasicMessageProducer_0_8] Sending content body frames to
direct://amq.direct//example.queue?routingkey='example.queue'&durable='true'
main 2008-08-26 11:17:58,249 DEBUG
[apache.qpid.client.BasicMessageProducer_0_8] Sending content header frame to
direct://amq.direct//example.queue?routingkey='example.queue'&durable='true'
main 2008-08-26 11:17:58,250 DEBUG [apache.qpid.framing.FieldTable]
FieldTable::writeToBuffer: Writing encoded length of 0...
main 2008-08-26 11:17:58,250 DEBUG [apache.qpid.framing.FieldTable] {}
main 2008-08-26 11:17:58,250 DEBUG [apache.qpid.framing.AMQDataBlockEncoder]
Encoded frame byte-buffer is
'0x01000100000020003c002800000a616d712e6469726563740d6578616d706c652e717565756501ce02000100000051003c00000000000000000007f9c00a746578742f706c61696e00000000000200002749443a30346535643663622d353731392d336663302d626635362d6230613933333433383435370000011bfe8510e9ce030001000000074d657373616765ce'
main 2008-08-26 11:17:58,251 DEBUG [qpid.protocol] SEND: [EMAIL PROTECTED]
org.apache.qpid.framing.CompositeAMQDataBlock{ 0=[Frame channelId: 1,
bodyFrame: [BasicPublishBodyImpl: ticket=0, exchange=amq.direct,
routingKey=example.queue, mandatory=true, immediate=false]] 1=[Frame channelId:
1, bodyFrame: [EMAIL PROTECTED] 2=[Frame channelId: 1, bodyFrame: [EMAIL
PROTECTED]
main 2008-08-26 11:17:58,252 INFO
[test.client.timeouts.SyncWaitTimeoutDelayTest] Calling Commit
main 2008-08-26 11:17:58,252 DEBUG [apache.qpid.framing.AMQDataBlockEncoder]
Encoded frame byte-buffer is '0x01000100000004005a0014ce'
main 2008-08-26 11:17:58,252 DEBUG [qpid.protocol] SEND: [EMAIL PROTECTED]
Frame channelId: 1, bodyFrame: [TxCommitBodyImpl: ]
main 2008-08-26 11:17:58,252 DEBUG [qpid.client.protocol.AMQProtocolHandler]
Blocking for:1000:org.apache.qpid.framing.TxCommitOkBody
> [AMQP-0-8/9] Client can incorrectly report CommitOK if previous commit timed
> out.
> ---------------------------------------------------------------------------------
>
> Key: QPID-1262
> URL: https://issues.apache.org/jira/browse/QPID-1262
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M2.1, M3
> Reporter: Martin Ritchie
>
> Summary:
> As shown by the new SyncWaitTimeoutDelayTest there is a bug in AMQP. The
> TxCommitOk bodies do not have a correlation id so it is impossible to tell if
> the TxCommitOk received is for the last TxCommit sent if you have timed out a
> previous commit.
> Attached is a log for this behaviour. As this is an AMQP bug it is unlikely
> we can resolve it in Qpid.
> Question is does 0-10 also exhibit this behaviour.
> Work around is to close the session after a commit timeout this will ensure
> that the TxCommitOk does not spuriously arrive on the client. It does however
> leave you unsure of the commit state, but presumably there was a reason you
> gave up waiting for the TxCommitOk and are prepared for the operation
> actually succeeding but never being notified about it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
