You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Guy Allard (JIRA)" <ji...@apache.org> on 2012/06/21 18:23:42 UTC
[jira] [Created] (AMQ-3892) NACKed Messages Are Not Available Later
Guy Allard created AMQ-3892:
-------------------------------
Summary: NACKed Messages Are Not Available Later
Key: AMQ-3892
URL: https://issues.apache.org/jira/browse/AMQ-3892
Project: ActiveMQ
Issue Type: Bug
Components: stomp
Affects Versions: 5.6.0
Environment: Linux tjjackson 3.0.0-21-generic #35-Ubuntu SMP Fri May 25 17:57:41 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Ruby stomp client - various versions
Reporter: Guy Allard
Attachments: snack.rb
connect
send a message
Subscribe with ackmode client.
Receive a message.
NACK it.
close connection
reestablish connection
resubscribe
attempt receive - message not available (and it should be)
I will attach example code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3892) NACKed Messages Are Not Available
Later
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399588#comment-13399588 ]
Timothy Bish commented on AMQ-3892:
-----------------------------------
You can now control this via the changes in AMQ-3894.
> NACKed Messages Are Not Available Later
> ---------------------------------------
>
> Key: AMQ-3892
> URL: https://issues.apache.org/jira/browse/AMQ-3892
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Affects Versions: 5.6.0
> Environment: Linux tjjackson 3.0.0-21-generic #35-Ubuntu SMP Fri May 25 17:57:41 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> Ruby stomp client - various versions
> Reporter: Guy Allard
> Attachments: snack.rb
>
>
> connect
> send a message
> Subscribe with ackmode client.
> Receive a message.
> NACK it.
> close connection
> reestablish connection
> resubscribe
> attempt receive - message not available (and it should be)
> I will attach example code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3892) NACKed Messages Are Not Available
Later
Posted by "Guy Allard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398760#comment-13398760 ]
Guy Allard commented on AMQ-3892:
---------------------------------
Thanks, makes sense.
Since servers are allowed several options with this, where is that documented please?
> NACKed Messages Are Not Available Later
> ---------------------------------------
>
> Key: AMQ-3892
> URL: https://issues.apache.org/jira/browse/AMQ-3892
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Affects Versions: 5.6.0
> Environment: Linux tjjackson 3.0.0-21-generic #35-Ubuntu SMP Fri May 25 17:57:41 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> Ruby stomp client - various versions
> Reporter: Guy Allard
> Attachments: snack.rb
>
>
> connect
> send a message
> Subscribe with ackmode client.
> Receive a message.
> NACK it.
> close connection
> reestablish connection
> resubscribe
> attempt receive - message not available (and it should be)
> I will attach example code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3892) NACKed Messages Are Not Available
Later
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398621#comment-13398621 ]
Timothy Bish commented on AMQ-3892:
-----------------------------------
A Stomp NACK is treated as a poison Ack and the message is sent to the DLQ.
> NACKed Messages Are Not Available Later
> ---------------------------------------
>
> Key: AMQ-3892
> URL: https://issues.apache.org/jira/browse/AMQ-3892
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Affects Versions: 5.6.0
> Environment: Linux tjjackson 3.0.0-21-generic #35-Ubuntu SMP Fri May 25 17:57:41 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> Ruby stomp client - various versions
> Reporter: Guy Allard
> Attachments: snack.rb
>
>
> connect
> send a message
> Subscribe with ackmode client.
> Receive a message.
> NACK it.
> close connection
> reestablish connection
> resubscribe
> attempt receive - message not available (and it should be)
> I will attach example code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AMQ-3892) NACKed Messages Are Not Available Later
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-3892.
-----------------------------
Resolution: Not A Problem
Working as designed.
> NACKed Messages Are Not Available Later
> ---------------------------------------
>
> Key: AMQ-3892
> URL: https://issues.apache.org/jira/browse/AMQ-3892
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Affects Versions: 5.6.0
> Environment: Linux tjjackson 3.0.0-21-generic #35-Ubuntu SMP Fri May 25 17:57:41 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> Ruby stomp client - various versions
> Reporter: Guy Allard
> Attachments: snack.rb
>
>
> connect
> send a message
> Subscribe with ackmode client.
> Receive a message.
> NACK it.
> close connection
> reestablish connection
> resubscribe
> attempt receive - message not available (and it should be)
> I will attach example code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3892) NACKed Messages Are Not Available Later
Posted by "Guy Allard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guy Allard updated AMQ-3892:
----------------------------
Attachment: snack.rb
Code to recreate this problem.
> NACKed Messages Are Not Available Later
> ---------------------------------------
>
> Key: AMQ-3892
> URL: https://issues.apache.org/jira/browse/AMQ-3892
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Affects Versions: 5.6.0
> Environment: Linux tjjackson 3.0.0-21-generic #35-Ubuntu SMP Fri May 25 17:57:41 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> Ruby stomp client - various versions
> Reporter: Guy Allard
> Attachments: snack.rb
>
>
> connect
> send a message
> Subscribe with ackmode client.
> Receive a message.
> NACK it.
> close connection
> reestablish connection
> resubscribe
> attempt receive - message not available (and it should be)
> I will attach example code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira