activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <>
Subject [jira] Commented: (AMQ-632) TaskRunnerFactory from broker is not carried along to Broker-to-Broker connections
Date Fri, 17 Mar 2006 12:01:26 GMT
    [ ] 

james strachan commented on AMQ-632:

Its a bit confusing isn't it :)

So the NetworkConnector creates the DemandForwardingBridge; so you should be able to configure
the it with the things you need like

 <networkConnector dispatchAsync="true">


(BTW true is the default in

There are a few different kinds of bridges available depending on the configurations of the
<networkConnector>. For added fun, the NetworkConnector class just got refactored; so
the concrete class that actually creates the bridge is DiscoveryNetworkConnector - see the
createBridge() method for details of how it figures out which bridge to use.

For demand forwarding I think you need to set <networkConnector conduitSubscriptions="false"

> TaskRunnerFactory from broker is not carried along to Broker-to-Broker connections
> ----------------------------------------------------------------------------------
>          Key: AMQ-632
>          URL:
>      Project: ActiveMQ
>         Type: Bug

>   Components: Broker
>     Versions: 4.0 M5
>     Reporter: Kevin Yaussy
>      Fix For: 4.0 M5
>  Attachments:
> When trying to enable dispatchAsync for broker-to-broker connections (which, since I've
not found a way to configure demandForwardingBridge in the broker XML, I had to hard code
by setting the default value of dispatchAsync in, I found that
the TaskRunnerFactory from the broker was not being carried through to the Network connections.
> I'm not sure if the way I fixed it is fully acceptable or not, however the attached
seems to fix the issue.  I changed doCompositeConnect to call setTaskRunnerFactory on the
newly created TransportConnector.
> The change is against SNAPSHOT 03/14/2006.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message