[
https://issues.apache.org/jira/browse/ARTEMIS-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276754#comment-17276754
]
ASF subversion and git services commented on ARTEMIS-3074:
----------------------------------------------------------
Commit ebeea15c2a8568952be8af2c4567ca5cf39898a8 in activemq-artemis's branch
refs/heads/master from Tomas Hofman
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ebeea15 ]
ARTEMIS-3074 Add ActiveMQServerControl#createBridge() method variant accepting
a JSON string
> Add ActiveMQServerControl#createBridge() method variant which accepts the
> callTimeout attribute
> -----------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3074
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3074
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.16.0
> Reporter: Tomas Hofman
> Priority: Major
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> Currently there are four variants of the
> {{ActiveMQServerControl#createBridge()}} method, none of which accepts the
> {{callTimeout}} attribute of the core bridge.
> The {{callTimeout}} attribute sets a call timeout for blocking calls to the
> server. Typically a bridge works in a non-blocking manner, but in some cases
> customers use configurations where calls do block.
> It would still be possible to set call timeout without this change using
> lower level API ({{ActiveMQServer#deployBridge()}}), but it would require
> duplicating some code which is already there in {{ActiveMQServerControl}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)