[exn-connector-java] A consumer is stopped, but only after processing one more message after being instructed to stop

Bug #2053126 reported by Andreas Tsagkaropoulos
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NebulOuS
Fix Released
Medium
Fotis Paraskevopoulos

Bug Description

During unregistration of a consumer, the ondelivery method is being called before actually stopping the consumer. The result is that one more message is (erroneously) processed before actually stopping the consumer. See the loop in lines 165-178 in the exn-connector/src/main/groovy/eu/nebulouscloud/exn/core/Manager.groovy file.

description: updated
Changed in nebulous:
assignee: nobody → Fotis Paraskevopoulos (forums-existanze)
importance: Undecided → Medium
tags: added: exn-connector-java
Changed in nebulous:
assignee: Fotis Paraskevopoulos (forums-existanze) → Fotis Paraskevopoulos (fotisparaskevopoulos)
Changed in nebulous:
status: New → Fix Committed
Changed in nebulous:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.