Bug 731043
Summary: | timeout waiting for sync | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Petr Matousek <pematous> |
Component: | qpid-java | Assignee: | Rajith Attapattu <rattapat+nobody> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Matousek <pematous> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 2.0 | CC: | iboverma, jross, lzhaldyb |
Target Milestone: | 2.3 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qpid-java-*-0.18-5 | Doc Type: | Bug Fix |
Doc Text: |
Cause:
delete for addressing does not work correctly.
it also appears that the delete was send for a queue instead of the exchange.
Consequence:
Client hangs due to waiting for a command completion on a session which was invalidated due to an exception. It eventually times out.
Fix:
Delete is only sent if the session is still valid.
Result:
The client will not hang anymore. However it will not issue a delete if the session is closed before the producer/consumer is closed.
It's recommended and good practise to first close the producers and consumers before closing the session (all though the session close should implicitly close producers and consumers). The ordered closing allows the JMS client to cleanup the resources correctly.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-19 16:40:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Matousek
2011-08-16 14:55:21 UTC
This issue has been fixed. Verified on rhel5.8 and rhel6.3 (x86_64, i386) packages used for testing: qpid-java-*-0.18-5 -> VERIFIED Petr, (Sorry I was on vacation and somehow missed this when I came back). I made changes to the address handling code which fixed a lot of minor bugs, especially the way we handled delete. It's a series of commits included in the 0.20 rebase. Delete is a tricky issue that cannot be completely fixed (true for all clients and JMS client has a few additional complications). For complications please see the comments on https://bugzilla.redhat.com/show_bug.cgi?id=876192 The following commit is largely responsible for this issue being fixed. http://svn.apache.org/viewvc?rev=1397651&view=rev Additionally we have also made changes during the last few cycles to error handling code. Rajith |