You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "alex hutter (JIRA)" <ji...@apache.org> on 2012/10/22 15:14:11 UTC
[jira] [Created] (CAMEL-5730) SqsConsumer receive thread is tightly
coupled to extendMessageVisiblity's scheduled task
alex hutter created CAMEL-5730:
----------------------------------
Summary: SqsConsumer receive thread is tightly coupled to extendMessageVisiblity's scheduled task
Key: CAMEL-5730
URL: https://issues.apache.org/jira/browse/CAMEL-5730
Project: Camel
Issue Type: Bug
Components: camel-aws
Affects Versions: 2.10.0
Reporter: alex hutter
When I made the patch file for CAMEL-5306 I made a mistake and coupled the cancelling of the visibility extending scheduled task with the thread that receives the message inside SqsConsumer. This causes issues when try to write Processors that delegate the completion of an exchange to another thread.
Actually the cancelling of the scheduled task should have been handled via exchange.addOnCompletion(), the same way the the overall SQS transaction is completed.
The attached patch fixes this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5730) SqsConsumer receive thread is
tightly coupled to extendMessageVisiblity's scheduled task
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-5730.
--------------------------------
Resolution: Fixed
Thanks for the patch.
> SqsConsumer receive thread is tightly coupled to extendMessageVisiblity's scheduled task
> ----------------------------------------------------------------------------------------
>
> Key: CAMEL-5730
> URL: https://issues.apache.org/jira/browse/CAMEL-5730
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
> Affects Versions: 2.10.0
> Reporter: alex hutter
> Assignee: Claus Ibsen
> Fix For: 2.10.3, 2.11.0
>
> Attachments: fix-SQS-timeout-extender.patch
>
>
> When I made the patch file for CAMEL-5306 I made a mistake and coupled the cancelling of the visibility extending scheduled task with the thread that receives the message inside SqsConsumer. This causes issues when try to write Processors that delegate the completion of an exchange to another thread.
> Actually the cancelling of the scheduled task should have been handled via exchange.addOnCompletion(), the same way the the overall SQS transaction is completed.
> The attached patch fixes this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5730) SqsConsumer receive thread is tightly
coupled to extendMessageVisiblity's scheduled task
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-5730:
-------------------------------
Fix Version/s: 2.11.0
2.10.3
> SqsConsumer receive thread is tightly coupled to extendMessageVisiblity's scheduled task
> ----------------------------------------------------------------------------------------
>
> Key: CAMEL-5730
> URL: https://issues.apache.org/jira/browse/CAMEL-5730
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
> Affects Versions: 2.10.0
> Reporter: alex hutter
> Assignee: Claus Ibsen
> Fix For: 2.10.3, 2.11.0
>
> Attachments: fix-SQS-timeout-extender.patch
>
>
> When I made the patch file for CAMEL-5306 I made a mistake and coupled the cancelling of the visibility extending scheduled task with the thread that receives the message inside SqsConsumer. This causes issues when try to write Processors that delegate the completion of an exchange to another thread.
> Actually the cancelling of the scheduled task should have been handled via exchange.addOnCompletion(), the same way the the overall SQS transaction is completed.
> The attached patch fixes this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-5730) SqsConsumer receive thread is
tightly coupled to extendMessageVisiblity's scheduled task
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-5730:
----------------------------------
Assignee: Claus Ibsen
> SqsConsumer receive thread is tightly coupled to extendMessageVisiblity's scheduled task
> ----------------------------------------------------------------------------------------
>
> Key: CAMEL-5730
> URL: https://issues.apache.org/jira/browse/CAMEL-5730
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
> Affects Versions: 2.10.0
> Reporter: alex hutter
> Assignee: Claus Ibsen
> Fix For: 2.10.3, 2.11.0
>
> Attachments: fix-SQS-timeout-extender.patch
>
>
> When I made the patch file for CAMEL-5306 I made a mistake and coupled the cancelling of the visibility extending scheduled task with the thread that receives the message inside SqsConsumer. This causes issues when try to write Processors that delegate the completion of an exchange to another thread.
> Actually the cancelling of the scheduled task should have been handled via exchange.addOnCompletion(), the same way the the overall SQS transaction is completed.
> The attached patch fixes this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5730) SqsConsumer receive thread is tightly
coupled to extendMessageVisiblity's scheduled task
Posted by "alex hutter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
alex hutter updated CAMEL-5730:
-------------------------------
Attachment: fix-SQS-timeout-extender.patch
I give permission for Apache to own the copyright on the attach file: fix-SQS-timeout-extender.patch
> SqsConsumer receive thread is tightly coupled to extendMessageVisiblity's scheduled task
> ----------------------------------------------------------------------------------------
>
> Key: CAMEL-5730
> URL: https://issues.apache.org/jira/browse/CAMEL-5730
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
> Affects Versions: 2.10.0
> Reporter: alex hutter
> Attachments: fix-SQS-timeout-extender.patch
>
>
> When I made the patch file for CAMEL-5306 I made a mistake and coupled the cancelling of the visibility extending scheduled task with the thread that receives the message inside SqsConsumer. This causes issues when try to write Processors that delegate the completion of an exchange to another thread.
> Actually the cancelling of the scheduled task should have been handled via exchange.addOnCompletion(), the same way the the overall SQS transaction is completed.
> The attached patch fixes this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira