[jira] Commented: (AMQ-632) TaskRunnerFactory from broker is not carried along to Broker-to-Broker connections

["james strachan (JIRA)" <ji...@activemq.org>]

    [ http://jira.activemq.org/jira//browse/AMQ-632?page=comments#action_35770 ] 

james strachan commented on AMQ-632:
------------------------------------

BTW there is a local and remote broker config in XML here which creates a demand forwarding bridge...

https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/network/

e.g. 

https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/network/localBroker.xml

> TaskRunnerFactory from broker is not carried along to Broker-to-Broker connections
> ----------------------------------------------------------------------------------
>
>          Key: AMQ-632
>          URL: http://jira.activemq.org/jira//browse/AMQ-632
>      Project: ActiveMQ
>         Type: Bug

>   Components: Broker
>     Versions: 4.0 M5
>     Reporter: Kevin Yaussy
>      Fix For: 4.0 M5
>  Attachments: VMTransportFactory.java
>
>
> 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 DemandForwardingBridge.java), 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 VMTransportFactory.java 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:
   http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira