[jira] [Commented] (QPID-8058) [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer of management temporary destination

2017-12-27 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/QPID-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16304579#comment-16304579
 ] 

ASF subversion and git services commented on QPID-8058:
---

Commit 4c8f854f14f655b377afce4df7a3ad28a6fc714c in qpid-broker-j's branch 
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=4c8f854 ]

QPID-8058: [Broker-J][AMQP 1.0] Fix draining of temporary message sources on 
management node

(cherry picked from commit 97ebcc8ef5f0a84a42af5d2eede374d27f2e61c6)
(cherry picked from commit 95d34b9224c8d5aab5bf55cabc721120994e42d6)


> [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer 
> of management temporary destination
> ---
>
> Key: QPID-8058
> URL: https://issues.apache.org/jira/browse/QPID-8058
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Keith Wall
> Fix For: qpid-java-broker-7.0.1
>
> Attachments: 
> TEST-org.apache.qpid.systest.management.amqp.AmqpManagementTest.testCreateQueueOnBrokerManagement.txt
>
>
> Test {{AmqpManagementTest.testCreateQueueOnBrokerManagement}} failed with the 
> following error:
> {noformat}
> org.apache.qpid.jms.JmsOperationTimedOutException: Remote did not respond to 
> a drain request in time
> {noformat}
> As per exception message, the client sent the Flow with drain=true but Broker 
> did not reply on it
> {noformat}
> 2017-12-05 18:20:13,950  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=2,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000,drain=true}
> {noformat}
> See the test log attached.
> Broker-J does not respond on flow performative with drain flag coming from 
> consumers of temporary destinations created on management nodes ($management).
> Test attached receiver link for temporary destination created on management 
> mode:
> {noformat}
> 2017-12-05 18:20:11,760  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Attach{name=qpid-jms:receiver:ID:0ea0fec9-455c-47db-b15e-4fd09c0c48d6:1:1:1:TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,handle=0,role=receiver,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,durable=none,expiryPolicy=link-detach,timeout=0,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
>  amqp:rejected:list, amqp:released:list, 
> amqp:modified:list],capabilities=[temporary-queue]},target=Target{}}
> 2017-12-05 18:20:11,763  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> SEND[/127.0.0.1:48726|1] : 
> Attach{name=qpid-jms:receiver:ID:0ea0fec9-455c-47db-b15e-4fd09c0c48d6:1:1:1:TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,handle=0,role=sender,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,durable=none,expiryPolicy=link-detach,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
>  amqp:released:list, 
> amqp:rejected:list],capabilities=[]},target=Target{},unsettled={},initialDeliveryCount=0,offeredCapabilities=[SHARED-SUBS],properties={}}
> {noformat}
> Granted credit
> {noformat}
> 2017-12-05 18:20:11,765  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=1,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000}
> {noformat}
> Broker sent Transfer
> {noformat}
> 2017-12-05 18:20:13,949  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> SEND[/127.0.0.1:48726|1] : 
> Transfer{handle=0,deliveryId=0,deliveryTag=\x00\x00\x00\x00\x00\x00\x00\x00,messageFormat=0}
> {noformat}
> and immediately after transfer received Flow with drain=true
> {noformat}
> 2017-12-05 18:20:13,950  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=2,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000,drain=true}
> {noformat}
> There was no message left on message source but broker did not send flow back.
> The existing implementation of {{ManagementNode#pullMessage}} does not notify 
> its {{ConsumerTarget}} when there is no messages left to send.
> Only users of AMQP management are affected by the bug.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: 

[jira] [Commented] (QPID-8058) [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer of management temporary destination

2017-12-22 Thread Keith Wall (JIRA)

[ 
https://issues.apache.org/jira/browse/QPID-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301644#comment-16301644
 ] 

Keith Wall commented on QPID-8058:
--

Looks okay to me, okay for porting.

> [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer 
> of management temporary destination
> ---
>
> Key: QPID-8058
> URL: https://issues.apache.org/jira/browse/QPID-8058
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Keith Wall
> Fix For: qpid-java-broker-7.0.1
>
> Attachments: 
> TEST-org.apache.qpid.systest.management.amqp.AmqpManagementTest.testCreateQueueOnBrokerManagement.txt
>
>
> Test {{AmqpManagementTest.testCreateQueueOnBrokerManagement}} failed with the 
> following error:
> {noformat}
> org.apache.qpid.jms.JmsOperationTimedOutException: Remote did not respond to 
> a drain request in time
> {noformat}
> As per exception message, the client sent the Flow with drain=true but Broker 
> did not reply on it
> {noformat}
> 2017-12-05 18:20:13,950  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=2,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000,drain=true}
> {noformat}
> See the test log attached.
> Broker-J does not respond on flow performative with drain flag coming from 
> consumers of temporary destinations created on management nodes ($management).
> Test attached receiver link for temporary destination created on management 
> mode:
> {noformat}
> 2017-12-05 18:20:11,760  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Attach{name=qpid-jms:receiver:ID:0ea0fec9-455c-47db-b15e-4fd09c0c48d6:1:1:1:TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,handle=0,role=receiver,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,durable=none,expiryPolicy=link-detach,timeout=0,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
>  amqp:rejected:list, amqp:released:list, 
> amqp:modified:list],capabilities=[temporary-queue]},target=Target{}}
> 2017-12-05 18:20:11,763  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> SEND[/127.0.0.1:48726|1] : 
> Attach{name=qpid-jms:receiver:ID:0ea0fec9-455c-47db-b15e-4fd09c0c48d6:1:1:1:TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,handle=0,role=sender,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,durable=none,expiryPolicy=link-detach,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
>  amqp:released:list, 
> amqp:rejected:list],capabilities=[]},target=Target{},unsettled={},initialDeliveryCount=0,offeredCapabilities=[SHARED-SUBS],properties={}}
> {noformat}
> Granted credit
> {noformat}
> 2017-12-05 18:20:11,765  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=1,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000}
> {noformat}
> Broker sent Transfer
> {noformat}
> 2017-12-05 18:20:13,949  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> SEND[/127.0.0.1:48726|1] : 
> Transfer{handle=0,deliveryId=0,deliveryTag=\x00\x00\x00\x00\x00\x00\x00\x00,messageFormat=0}
> {noformat}
> and immediately after transfer received Flow with drain=true
> {noformat}
> 2017-12-05 18:20:13,950  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=2,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000,drain=true}
> {noformat}
> There was no message left on message source but broker did not send flow back.
> The existing implementation of {{ManagementNode#pullMessage}} does not notify 
> its {{ConsumerTarget}} when there is no messages left to send.
> Only users of AMQP management are affected by the bug.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Commented] (QPID-8058) [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer of management temporary destination

2017-12-14 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/QPID-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290839#comment-16290839
 ] 

ASF subversion and git services commented on QPID-8058:
---

Commit 95d34b9224c8d5aab5bf55cabc721120994e42d6 in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=95d34b9 ]

QPID-8058: [Broker-J] Address review comments


> [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer 
> of management temporary destination
> ---
>
> Key: QPID-8058
> URL: https://issues.apache.org/jira/browse/QPID-8058
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Keith Wall
> Fix For: qpid-java-broker-7.0.1
>
> Attachments: 
> TEST-org.apache.qpid.systest.management.amqp.AmqpManagementTest.testCreateQueueOnBrokerManagement.txt
>
>
> Test {{AmqpManagementTest.testCreateQueueOnBrokerManagement}} failed with the 
> following error:
> {noformat}
> org.apache.qpid.jms.JmsOperationTimedOutException: Remote did not respond to 
> a drain request in time
> {noformat}
> As per exception message, the client sent the Flow with drain=true but Broker 
> did not reply on it
> {noformat}
> 2017-12-05 18:20:13,950  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=2,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000,drain=true}
> {noformat}
> See the test log attached.
> Broker-J does not respond on flow performative with drain flag coming from 
> consumers of temporary destinations created on management nodes ($management).
> Test attached receiver link for temporary destination created on management 
> mode:
> {noformat}
> 2017-12-05 18:20:11,760  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Attach{name=qpid-jms:receiver:ID:0ea0fec9-455c-47db-b15e-4fd09c0c48d6:1:1:1:TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,handle=0,role=receiver,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,durable=none,expiryPolicy=link-detach,timeout=0,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
>  amqp:rejected:list, amqp:released:list, 
> amqp:modified:list],capabilities=[temporary-queue]},target=Target{}}
> 2017-12-05 18:20:11,763  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> SEND[/127.0.0.1:48726|1] : 
> Attach{name=qpid-jms:receiver:ID:0ea0fec9-455c-47db-b15e-4fd09c0c48d6:1:1:1:TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,handle=0,role=sender,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,durable=none,expiryPolicy=link-detach,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
>  amqp:released:list, 
> amqp:rejected:list],capabilities=[]},target=Target{},unsettled={},initialDeliveryCount=0,offeredCapabilities=[SHARED-SUBS],properties={}}
> {noformat}
> Granted credit
> {noformat}
> 2017-12-05 18:20:11,765  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=1,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000}
> {noformat}
> Broker sent Transfer
> {noformat}
> 2017-12-05 18:20:13,949  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> SEND[/127.0.0.1:48726|1] : 
> Transfer{handle=0,deliveryId=0,deliveryTag=\x00\x00\x00\x00\x00\x00\x00\x00,messageFormat=0}
> {noformat}
> and immediately after transfer received Flow with drain=true
> {noformat}
> 2017-12-05 18:20:13,950  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=2,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000,drain=true}
> {noformat}
> There was no message left on message source but broker did not send flow back.
> The existing implementation of {{ManagementNode#pullMessage}} does not notify 
> its {{ConsumerTarget}} when there is no messages left to send.
> Only users of AMQP management are affected by the bug.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Commented] (QPID-8058) [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer of management temporary destination

2017-12-11 Thread Keith Wall (JIRA)

[ 
https://issues.apache.org/jira/browse/QPID-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16286043#comment-16286043
 ] 

Keith Wall commented on QPID-8058:
--

I think the change looks reasonable to me.  I think this problem would only 
affect a user who is trying to use AMQP Management (WD) - not AMQP in general - 
like always the JIRA should say as much.

Separately, shouldn't {{AbstractSystemMessageSource#pullMessage}} have the same 
pattern?

> [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer 
> of management temporary destination
> ---
>
> Key: QPID-8058
> URL: https://issues.apache.org/jira/browse/QPID-8058
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Keith Wall
> Fix For: qpid-java-broker-7.0.1
>
> Attachments: 
> TEST-org.apache.qpid.systest.management.amqp.AmqpManagementTest.testCreateQueueOnBrokerManagement.txt
>
>
> Test {{AmqpManagementTest.testCreateQueueOnBrokerManagement}} failed with the 
> following error:
> {noformat}
> org.apache.qpid.jms.JmsOperationTimedOutException: Remote did not respond to 
> a drain request in time
> {noformat}
> As per exception message, the client sent the Flow with drain=true but Broker 
> did not reply on it
> {noformat}
> 2017-12-05 18:20:13,950  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=2,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000,drain=true}
> {noformat}
> See the test log attached.
> Broker-J does not respond on flow performative with drain flag coming from 
> consumers of temporary destinations created on management nodes ($management).
> Test attached receiver link for temporary destination created on management 
> mode:
> {noformat}
> 2017-12-05 18:20:11,760  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Attach{name=qpid-jms:receiver:ID:0ea0fec9-455c-47db-b15e-4fd09c0c48d6:1:1:1:TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,handle=0,role=receiver,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,durable=none,expiryPolicy=link-detach,timeout=0,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
>  amqp:rejected:list, amqp:released:list, 
> amqp:modified:list],capabilities=[temporary-queue]},target=Target{}}
> 2017-12-05 18:20:11,763  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> SEND[/127.0.0.1:48726|1] : 
> Attach{name=qpid-jms:receiver:ID:0ea0fec9-455c-47db-b15e-4fd09c0c48d6:1:1:1:TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,handle=0,role=sender,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,durable=none,expiryPolicy=link-detach,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
>  amqp:released:list, 
> amqp:rejected:list],capabilities=[]},target=Target{},unsettled={},initialDeliveryCount=0,offeredCapabilities=[SHARED-SUBS],properties={}}
> {noformat}
> Granted credit
> {noformat}
> 2017-12-05 18:20:11,765  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=1,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000}
> {noformat}
> Broker sent Transfer
> {noformat}
> 2017-12-05 18:20:13,949  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> SEND[/127.0.0.1:48726|1] : 
> Transfer{handle=0,deliveryId=0,deliveryTag=\x00\x00\x00\x00\x00\x00\x00\x00,messageFormat=0}
> {noformat}
> and immediately after transfer received Flow with drain=true
> {noformat}
> 2017-12-05 18:20:13,950  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=2,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000,drain=true}
> {noformat}
> There was no message left on destination but broker did not send flow back.
> The existing implementation of {{ManagementNode#pullMessage}} does not notify 
> its {{ConsumerTarget}} when there is no messages left to send.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Commented] (QPID-8058) [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer of management temporary destination

2017-12-08 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/QPID-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283722#comment-16283722
 ] 

ASF subversion and git services commented on QPID-8058:
---

Commit 97ebcc8ef5f0a84a42af5d2eede374d27f2e61c6 in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=97ebcc8 ]

QPID-8058: [Broker-J][AMQP 1.0] Fix draining of temporary message sources on 
management node


> [Broker-J][AMQP 1.0] Broker does not respond to drain request from consumer 
> of management temporary destination
> ---
>
> Key: QPID-8058
> URL: https://issues.apache.org/jira/browse/QPID-8058
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
> Fix For: qpid-java-broker-7.0.1
>
> Attachments: 
> TEST-org.apache.qpid.systest.management.amqp.AmqpManagementTest.testCreateQueueOnBrokerManagement.txt
>
>
> Test {{AmqpManagementTest.testCreateQueueOnBrokerManagement}} failed with the 
> following error:
> {noformat}
> org.apache.qpid.jms.JmsOperationTimedOutException: Remote did not respond to 
> a drain request in time
> {noformat}
> As per exception message, the client sent the Flow with drain=true but Broker 
> did not reply on it
> {noformat}
> 2017-12-05 18:20:13,950  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=2,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000,drain=true}
> {noformat}
> See the test log attached.
> Broker-J does not respond on flow performative with drain flag coming from 
> consumers of temporary destinations created on management nodes ($management).
> Test attached receiver link for temporary destination created on management 
> mode:
> {noformat}
> 2017-12-05 18:20:11,760  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Attach{name=qpid-jms:receiver:ID:0ea0fec9-455c-47db-b15e-4fd09c0c48d6:1:1:1:TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,handle=0,role=receiver,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,durable=none,expiryPolicy=link-detach,timeout=0,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
>  amqp:rejected:list, amqp:released:list, 
> amqp:modified:list],capabilities=[temporary-queue]},target=Target{}}
> 2017-12-05 18:20:11,763  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> SEND[/127.0.0.1:48726|1] : 
> Attach{name=qpid-jms:receiver:ID:0ea0fec9-455c-47db-b15e-4fd09c0c48d6:1:1:1:TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,handle=0,role=sender,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=TempQueuecdf2fb78-beda-4456-9e2c-dd2dd4d9a53e,durable=none,expiryPolicy=link-detach,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
>  amqp:released:list, 
> amqp:rejected:list],capabilities=[]},target=Target{},unsettled={},initialDeliveryCount=0,offeredCapabilities=[SHARED-SUBS],properties={}}
> {noformat}
> Granted credit
> {noformat}
> 2017-12-05 18:20:11,765  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=1,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000}
> {noformat}
> Broker sent Transfer
> {noformat}
> 2017-12-05 18:20:13,949  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> SEND[/127.0.0.1:48726|1] : 
> Transfer{handle=0,deliveryId=0,deliveryTag=\x00\x00\x00\x00\x00\x00\x00\x00,messageFormat=0}
> {noformat}
> and immediately after transfer received Flow with drain=true
> {noformat}
> 2017-12-05 18:20:13,950  DEBUG [IO-/127.0.0.1:48726] o.a.q.s.p.frame 
> RECV[/127.0.0.1:48726|1] : 
> Flow{nextIncomingId=0,incomingWindow=2047,nextOutgoingId=2,outgoingWindow=2147483647,handle=0,deliveryCount=0,linkCredit=1000,drain=true}
> {noformat}
> There was no message left on destination but broker did not send flow back.
> The existing implementation of {{ManagementNode#pullMessage}} does not notify 
> its {{ConsumerTarget}} when there is no messages left to send.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org