Bug 1132182 - [GSS] (6.3.1) The returnBlocking() method should propagate the exception in the fail method or RemottingConnection.
Summary: [GSS] (6.3.1) The returnBlocking() method should propagate the exception in t...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.3.1
Assignee: Clebert Suconic
QA Contact: Miroslav Novak
Russell Dickenson
URL:
Whiteboard:
Depends On: 1128804
Blocks: eap631-blockers, eap631-payload, eap63-cp01-blockers 1132169
TreeView+ depends on / blocked
 
Reported: 2014-08-20 20:58 UTC by Jimmy Wilson
Modified: 2018-12-06 17:49 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1128804
Environment:
Last Closed: 2014-10-13 18:39:27 UTC
Type: Enhancement

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HORNETQ-1388 0 Major Closed The returnBlocking() method should propagate the exception in the fail method or RemotingConnection. 2015-11-02 08:37:33 UTC

Description Jimmy Wilson 2014-08-20 20:58:16 UTC 
+++ This bug was initially created as a clone of Bug #1128804 +++

At the moment when connection fails the exception is passed to fail() method that deal with the connection failure but tho exception is not propagated tot client, it's only send to exception listeners. It would be helpful if it was pass to client via returnBlocking method.

--- Additional comment from JBoss JIRA Server on 2014-08-12 16:11:39 EDT ---

Justin Bertram <jbertram> updated the status of jira HORNETQ-1388 to Resolved

--- Additional comment from JBoss JIRA Server on 2014-08-12 16:11:49 EDT ---

Justin Bertram <jbertram> updated the status of jira HORNETQ-1388 to Closed

--- Additional comment from  on 2014-08-12 16:12:57 EDT ---

This has been resolved on the 2.3.x branch of HornetQ via 7a8e2fa11670093d34290c46e804dbd1ba51504c.
Comment 2 Martin Svehla 2014-09-01 10:05:46 UTC 
We can now see in our failover tests that HornetQ is correctly returning cause exception in the error. Verified with EAP 6.3.1.CP.CR1
Note You need to log in before you can comment on or make changes to this bug.