subject:"\[jira\] \[Updated\] \(DISPATCH\-1090\) Transfer\/Disposition\(state=release\) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted."

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

2018-07-27 Thread Ted Ross (JIRA)



 [ 
https://issues.apache.org/jira/browse/DISPATCH-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross updated DISPATCH-1090:
---
Fix Version/s: Backlog

> Transfer/Disposition(state=release) loop forms when application disconnects 
> abruptly from brokered queue until link credit is exhausted.
> 
>
> Key: DISPATCH-1090
> URL: https://issues.apache.org/jira/browse/DISPATCH-1090
> Project: Qpid Dispatch
>  Issue Type: Bug
> Environment: Version  1.3.0-SNAPSHOT
>  (30ff7ff1d54b8f280b36f76dc8c340cb4c88567b)
>Reporter: Keith Wall
>Priority: Major
> Fix For: Backlog
>
> Attachments: DISPATCH-1090_dispatch_server.log
>
>
> I have configured a single Dispatch Router instance to route messages through 
> a broker queue (i.e. following section 7.2.5 of the 
> [docs|https://qpid.apache.org/releases/qpid-dispatch-1.2.0/user-guide/index.html#routing-messages-through-broker]).
> The application does the following:
> # Forms a sending links to the queue, sends a single message then disconnects.
> # Forms a receiving link to the same queue, receives the message without 
> settling then abruptly terminates the program.
> Inspecting the protocol trace, I see that after the Dispatch Router has sent 
> a {{Disposition state=modified}} for the message that was held by the 
> application when it terminated, a {{Transfer}}/{{Disposition state=release}} 
> loop forms between the Dispatch Router and Broker until the link credit is 
> exhausted.  
> Protocol trace attached to this issue demonstrates the problem.
> Dispatch Router was configured by the following commands:
> {noformat}
> qdmanage create --type org.apache.qpid.dispatch.connector host=oslo.local 
> port=5672 name=artemis-broker role=route-container
> qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink 
> addr=queue direction=in connection=artemis-broker
> qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink 
> addr=queue direction=out connection=artemis-broker
> qdmanage create --type=org.apache.qpid.dispatch.router.config.address 
> pattern=queue waypoint=true
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

2018-07-27 Thread Keith Wall (JIRA)



 [ 
https://issues.apache.org/jira/browse/DISPATCH-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall updated DISPATCH-1090:
-
Description: 
I have configured a single Dispatch Router instance to route messages through a 
broker queue (i.e. following section 7.2.5 of the 
[docs|https://qpid.apache.org/releases/qpid-dispatch-1.2.0/user-guide/index.html#routing-messages-through-broker]).

The application does the following:

# Forms a sending links to the queue, sends a single message then disconnects.
# Forms a receiving link to the same queue, receives the message without 
settling then abruptly terminates the program.

Inspecting the protocol trace, I see that after the Dispatch Router has sent a 
{{Disposition state=modified}} for the message that was held by the application 
when it terminated, a {{Transfer}}/{{Disposition state=release}} loop forms 
between the Dispatch Router and Broker until the link credit is exhausted.  

Protocol trace attached to this issue demonstrates the problem.

Dispatch Router was configured by the following commands:

{noformat}
qdmanage create --type org.apache.qpid.dispatch.connector host=oslo.local 
port=5672 name=artemis-broker role=route-container
qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink 
addr=queue direction=in connection=artemis-broker
qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink 
addr=queue direction=out connection=artemis-broker
qdmanage create --type=org.apache.qpid.dispatch.router.config.address 
pattern=queue waypoint=true
{noformat}






  was:
I have configured a single Dispatch Router instance to route messages through a 
broker queue (i.e. following section 7.2.5 of the 
[docs|https://qpid.apache.org/releases/qpid-dispatch-1.2.0/user-guide/index.html#routing-messages-through-broker]).

The application does the following:

# Forms a sending links to the queue, sends a single message then disconnects.
# Forms a receiving link to the same queue, receives the message without 
settling then abruptly terminates the program.

Inspecting the protocol trace, I see that after the Dispatch Router has sent a 
{{Disposition state=modified}} for the message that was held by the application 
when it terminated, a {{Transfer}}/{{Disposition state=release}} loop forms 
between the Dispatch Router and Broker until the link credit is exhausted.  







> Transfer/Disposition(state=release) loop forms when application disconnects 
> abruptly from brokered queue until link credit is exhausted.
> 
>
> Key: DISPATCH-1090
> URL: https://issues.apache.org/jira/browse/DISPATCH-1090
> Project: Qpid Dispatch
>  Issue Type: Bug
> Environment: Version  1.3.0-SNAPSHOT
>  (30ff7ff1d54b8f280b36f76dc8c340cb4c88567b)
>Reporter: Keith Wall
>Priority: Major
> Attachments: DISPATCH-1090_dispatch_server.log
>
>
> I have configured a single Dispatch Router instance to route messages through 
> a broker queue (i.e. following section 7.2.5 of the 
> [docs|https://qpid.apache.org/releases/qpid-dispatch-1.2.0/user-guide/index.html#routing-messages-through-broker]).
> The application does the following:
> # Forms a sending links to the queue, sends a single message then disconnects.
> # Forms a receiving link to the same queue, receives the message without 
> settling then abruptly terminates the program.
> Inspecting the protocol trace, I see that after the Dispatch Router has sent 
> a {{Disposition state=modified}} for the message that was held by the 
> application when it terminated, a {{Transfer}}/{{Disposition state=release}} 
> loop forms between the Dispatch Router and Broker until the link credit is 
> exhausted.  
> Protocol trace attached to this issue demonstrates the problem.
> Dispatch Router was configured by the following commands:
> {noformat}
> qdmanage create --type org.apache.qpid.dispatch.connector host=oslo.local 
> port=5672 name=artemis-broker role=route-container
> qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink 
> addr=queue direction=in connection=artemis-broker
> qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink 
> addr=queue direction=out connection=artemis-broker
> qdmanage create --type=org.apache.qpid.dispatch.router.config.address 
> pattern=queue waypoint=true
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

2018-07-27 Thread Keith Wall (JIRA)



 [ 
https://issues.apache.org/jira/browse/DISPATCH-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall updated DISPATCH-1090:
-
Environment: 
Version  1.3.0-SNAPSHOT
 (30ff7ff1d54b8f280b36f76dc8c340cb4c88567b)



> Transfer/Disposition(state=release) loop forms when application disconnects 
> abruptly from brokered queue until link credit is exhausted.
> 
>
> Key: DISPATCH-1090
> URL: https://issues.apache.org/jira/browse/DISPATCH-1090
> Project: Qpid Dispatch
>  Issue Type: Bug
> Environment: Version  1.3.0-SNAPSHOT
>  (30ff7ff1d54b8f280b36f76dc8c340cb4c88567b)
>Reporter: Keith Wall
>Priority: Major
> Attachments: DISPATCH-1090_dispatch_server.log
>
>
> I have configured a single Dispatch Router instance to route messages through 
> a broker queue (i.e. following section 7.2.5 of the 
> [docs|https://qpid.apache.org/releases/qpid-dispatch-1.2.0/user-guide/index.html#routing-messages-through-broker]).
> The application does the following:
> # Forms a sending links to the queue, sends a single message then disconnects.
> # Forms a receiving link to the same queue, receives the message without 
> settling then abruptly terminates the program.
> Inspecting the protocol trace, I see that after the Dispatch Router has sent 
> a {{Disposition state=modified}} for the message that was held by the 
> application when it terminated, a {{Transfer}}/{{Disposition state=release}} 
> loop forms between the Dispatch Router and Broker until the link credit is 
> exhausted.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

2018-07-27 Thread Keith Wall (JIRA)



 [ 
https://issues.apache.org/jira/browse/DISPATCH-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall updated DISPATCH-1090:
-
Description: 
I have configured a single Dispatch Router instance to route messages through a 
broker queue (i.e. following section 7.2.5 of the 
[docs|https://qpid.apache.org/releases/qpid-dispatch-1.2.0/user-guide/index.html#routing-messages-through-broker]).

The application does the following:

# Forms a sending links to the queue, sends a single message then disconnects.
# Forms a receiving link to the same queue, receives the message without 
settling then abruptly terminates the program.

Inspecting the protocol trace, I see that after the Dispatch Router has sent a 
{{Disposition state=modified}} for the message that was held by the application 
when it terminated, a {{Transfer}}/{{Disposition state=release}} loop forms 
between the Dispatch Router and Broker until the link credit is exhausted.  






  was:
I have configured a single Dispatch Router instance to route messages through a 
broker queue (i.e. following section 7.2.5 of the 
[docs|https://qpid.apache.org/releases/qpid-dispatch-1.2.0/user-guide/index.html#routing-messages-through-broker]).

The application does the following:

# Forms a sending links to the queue, sends a single message then disconnects.
# Forms a receiving link to the same queue, receives the message without 
settling then abruptly terminates the program.

Inspecting the protocol trace, I see that after the Dispatch Router has sent a 
{{Disposition state=modified}} for the message that was held by the application 
when it terminated, a {{Transfer}}/{{Disposition state=release}} loop forms 
between the Dispatch Router and Broker until the link credit is exhausted.  





The application connects sends to the queue via the router, disconnects and the 
then connects a second time


> Transfer/Disposition(state=release) loop forms when application disconnects 
> abruptly from brokered queue until link credit is exhausted.
> 
>
> Key: DISPATCH-1090
> URL: https://issues.apache.org/jira/browse/DISPATCH-1090
> Project: Qpid Dispatch
>  Issue Type: Bug
>Reporter: Keith Wall
>Priority: Major
> Attachments: DISPATCH-1090_dispatch_server.log
>
>
> I have configured a single Dispatch Router instance to route messages through 
> a broker queue (i.e. following section 7.2.5 of the 
> [docs|https://qpid.apache.org/releases/qpid-dispatch-1.2.0/user-guide/index.html#routing-messages-through-broker]).
> The application does the following:
> # Forms a sending links to the queue, sends a single message then disconnects.
> # Forms a receiving link to the same queue, receives the message without 
> settling then abruptly terminates the program.
> Inspecting the protocol trace, I see that after the Dispatch Router has sent 
> a {{Disposition state=modified}} for the message that was held by the 
> application when it terminated, a {{Transfer}}/{{Disposition state=release}} 
> loop forms between the Dispatch Router and Broker until the link credit is 
> exhausted.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

2018-07-27 Thread Keith Wall (JIRA)



 [ 
https://issues.apache.org/jira/browse/DISPATCH-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall updated DISPATCH-1090:
-
Attachment: DISPATCH-1090_dispatch_server.log

> Transfer/Disposition(state=release) loop forms when application disconnects 
> abruptly from brokered queue until link credit is exhausted.
> 
>
> Key: DISPATCH-1090
> URL: https://issues.apache.org/jira/browse/DISPATCH-1090
> Project: Qpid Dispatch
>  Issue Type: Bug
>Reporter: Keith Wall
>Priority: Major
> Attachments: DISPATCH-1090_dispatch_server.log
>
>
> I have configured a single Dispatch Router instance to route messages through 
> a broker queue (i.e. following section 7.2.5 of the 
> [docs|https://qpid.apache.org/releases/qpid-dispatch-1.2.0/user-guide/index.html#routing-messages-through-broker]).
> The application does the following:
> # Forms a sending links to the queue, sends a single message then disconnects.
> # Forms a receiving link to the same queue, receives the message without 
> settling then abruptly terminates the program.
> Inspecting the protocol trace, I see that after the Dispatch Router has sent 
> a {{Disposition state=modified}} for the message that was held by the 
> application when it terminated, a {{Transfer}}/{{Disposition state=release}} 
> loop forms between the Dispatch Router and Broker until the link credit is 
> exhausted.  
> The application connects sends to the queue via the router, disconnects and 
> the then connects a second time



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

5 matches

Site Navigation

Mail list logo

Footer information