Robbie,
Yes we are seeing a failure in that the messages are not delivered.
When talking to Azure Service Bus the process hangs on the first attempt of
send. From the log it looks like the send attempt happens before the
receipt of a FLOW, is there some option I need to set to ensure this happens
first?
2015-06-26 10:44:04,796 [dows.net:5671/]] - TRACE AmqpProvider
- New Proton Event: LINK_INIT
2015-06-26 10:44:04,796 [dows.net:5671/]] - TRACE AmqpProvider
- New Proton Event: LINK_LOCAL_OPEN
2015-06-26 10:44:04,796 [dows.net:5671/]] - TRACE AmqpProvider
- New Proton Event: LINK_REMOTE_OPEN
2015-06-26 10:44:04,811 [dows.net:5671/]] - DEBUG AmqpAbstractResource
- AmqpFixedProducer { ID:WIN81CLIENT-58486-1435279438889-0:1:1:1 } is now
open:
2015-06-26 10:44:04,827 [dows.net:5671/]] - TRACE AmqpFixedProducer
- Holding Message send until credit is available.
2015-06-26 10:44:05,124 [ntLoopGroup-2-1] - TRACE NettyTcpTransport
- New data read: 35 bytes incoming: UnpooledHeapByteBuf(ridx: 0, widx: 35,
cap: 69)
2015-06-26 10:44:05,124 [dows.net:5671/]] - INFO BYTES
- Recieved:
0000002302000001005313c0160b520143520170000007fe434370000003e843404240
2015-06-26 10:44:05,124 [dows.net:5671/]] - TRACE FRAMES
- RECV: Flow{nextIncomingId=1, incomingWindow=0, nextOutgoingId=1,
outgoingWindow=2046, handle=0, deliveryCount=0, linkCredit=1000,
available=0, drain=false, echo=false, properties=null}
2015-06-26 10:44:05,124 [dows.net:5671/]] - TRACE AmqpProvider
- New Proton Event: LINK_FLOW
2015-06-26 10:44:05,124 [dows.net:5671/]] - TRACE AmqpFixedProducer
- Dispatching previously held send
2015-06-26 10:44:05,124 [dows.net:5671/]] - TRACE AmqpFixedProducer
- Producer sending message: JmsOutboundMessageDispatch {dispatchId =
ID:WIN81CLIENT-58486-1435279438889-0:1:1:1-1}
2015-06-26 10:44:57,343 [ntLoopGroup-2-1] - TRACE NettyTcpTransport
- New data read: 8 bytes incoming: UnpooledHeapByteBuf(ridx: 0, widx: 8,
cap: 37)
2015-06-26 10:44:57,343 [dows.net:5671/]] - INFO BYTES
- Recieved: 0000000802000000
2015-06-26 10:45:49,906 [ntLoopGroup-2-1] - TRACE NettyTcpTransport
- New data read: 8 bytes incoming: UnpooledHeapByteBuf(ridx: 0, widx: 8,
cap: 37)
2015-06-26 10:45:49,906 [dows.net:5671/]] - INFO BYTES
- Recieved: 0000000802000000
Yet in the case of Windows Service Bus, which for our test is hosted in an
Azure VM, we can successfully send 50 of 100 messages but then get into the
same "no credit". In this case the FLOW is received before the first
attempted message send:
2015-06-26 11:06:07,387 [dapp.net:8671/]] - TRACE AmqpProvider
- New Proton Event: LINK_INIT
2015-06-26 11:06:07,387 [dapp.net:8671/]] - TRACE AmqpProvider
- New Proton Event: LINK_LOCAL_OPEN
2015-06-26 11:06:07,387 [dapp.net:8671/]] - TRACE AmqpProvider
- New Proton Event: LINK_REMOTE_OPEN
2015-06-26 11:06:07,387 [dapp.net:8671/]] - DEBUG AmqpAbstractResource
- AmqpFixedProducer { ID:WIN81CLIENT-58513-1435280763074-0:1:1:1 } is now
open:
2015-06-26 11:06:07,387 [dapp.net:8671/]] - INFO BYTES
- Recieved: 0000001c02000001005313c00f0b5201435201434343523243404240
2015-06-26 11:06:07,387 [dapp.net:8671/]] - TRACE FRAMES
- RECV: Flow{nextIncomingId=1, incomingWindow=0, nextOutgoingId=1,
outgoingWindow=0, handle=0, deliveryCount=0, linkCredit=50, available=0,
drain=false, echo=false, properties=null}
2015-06-26 11:06:07,387 [dapp.net:8671/]] - TRACE AmqpProvider
- New Proton Event: LINK_FLOW
2015-06-26 11:06:07,402 [dapp.net:8671/]] - TRACE AmqpFixedProducer
- Producer sending message: JmsOutboundMessageDispatch {dispatchId =
ID:WIN81CLIENT-58513-1435280763074-0:1:1:1-1}
2015-06-26 11:06:07,418 [dapp.net:8671/]] - TRACE AmqpFixedProducer
- Producer sending message: JmsOutboundMessageDispatch {dispatchId =
ID:WIN81CLIENT-58513-1435280763074-0:1:1:1-2}
Sent message with JMSMessageID =
ID:WIN81CLIENT-58513-1435280763074-0:1:1:1-2
2015-06-26 11:06:07,527 [dapp.net:8671/]] - TRACE AmqpFixedProducer
- Producer sending message: JmsOutboundMessageDispatch {dispatchId =
ID:WIN81CLIENT-58513-1435280763074-0:1:1:1-3}
Sent message with JMSMessageID =
ID:WIN81CLIENT-58513-1435280763074-0:1:1:1-3
Cheers
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Qpid-JMS-0-3-0-Holding-message-send-until-credit-is-available-tp7627277p7627300.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
