Bug 1205490 - (6.2.0) JMS reference binding always works even if destination throws exception
Summary: (6.2.0) JMS reference binding always works even if destination throws exception
Keywords:
Status: MODIFIED
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: SwitchYard
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: tcunning
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-25 03:09 UTC by Tadayoshi Sato
Modified: 2019-04-16 14:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SWITCHYARD-1950 0 Major Resolved for IN_ONLY, ClientProxyBean and camel OutboundHandler doesn't propagate a fault to the consumer 2018-01-15 07:56:36 UTC

Description Tadayoshi Sato 2015-03-25 03:09:05 UTC
Platform BZ for https://issues.jboss.org/browse/SWITCHYARD-1950

Please make sure SWITCHYARD-1950 is fixed in FSW 6.2.

Here is the issue description. In a SwitchYard application, I have this Camel route:

from("switchyard://SampleService")
  .doTry()
    .log("Received message for 'SampleService' : ${body}")
    .to("switchyard://JmsQueueReference")
    .log("BODY ======> ${body}")
    [...]

The binding to "JmsQueueReference" always works, even if the JMS queue associated with the binding does not exist in JBoss EAP.

The reference binding has the following Java interface that has IN_ONLY MEP:

public interface QueueReference {
    void process(Transaction transaction);
}


Note You need to log in before you can comment on or make changes to this bug.