This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-performance-tests.git
commit 95738108d53346e8b2de7f625dd44560f93a20fb Author: Claus Ibsen <[email protected]> AuthorDate: Sun Oct 18 14:50:40 2026 +0200 ai-benchmark: jms-request-reply step 1 restarts the integration A reload does not apply new camel.beans.* and camel.component.* properties: the jms component it creates has no connection factory ("connectionFactory must be specified", jref1), so connecting to Artemis needs a restart, and the step says so, as the Java class steps do. Reference pass 4/4 in three runs. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m --- ai-benchmark/gen_stepwise.py | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/ai-benchmark/gen_stepwise.py b/ai-benchmark/gen_stepwise.py index 1d4da6b..5101b1b 100644 --- a/ai-benchmark/gen_stepwise.py +++ b/ai-benchmark/gen_stepwise.py @@ -883,9 +883,11 @@ EXAMPLES.append({ "seed": "connect-service-jms-request-reply", "infra": ["artemis"], "steps_dir": NEW, "initial": {JR: jr_s1, "application.properties": "# application properties\n"}, "steps": [ - {"request": "Connect to the ActiveMQ Artemis broker that camel infra started (tcp://localhost:61616, user artemis, password artemis) and send each order to the queue orders with the jms component, logging \"Order ${header.orderId} put on the queue\" instead of received. Add a route reserve-order that takes the orders off the queue and logs \"Reserving ${header.orderId} for customer ${header.customer}\".", + {"request": "Connect to the ActiveMQ Artemis broker that camel infra started (tcp://localhost:61616, user artemis, password artemis) and send each order to the queue orders with the jms component, logging \"Order ${header.orderId} put on the queue\" instead of received. Add a route reserve-order that takes the orders off the queue and logs \"Reserving ${header.orderId} for customer ${header.customer}\". The integration is restarted after your change, so new connection settings apply.", + # a reload does not apply new camel.beans.* and camel.component.* properties: the jms component it creates has + # no connection factory ("connectionFactory must be specified", jref1, Oct 18), so this step restarts "check": {"log_regex": ["Order ORD-1001 put on the queue", "Reserving ORD-1001 for customer C-482"]}, - "reference": {JR: jr_s2, "application.properties": JR_CF}}, + "reference": {JR: jr_s2, "application.properties": JR_CF}, "restart": True}, {"request": "Add a route stock-service on the queue stock that answers whether an order (the JSON body) can be reserved: \"reserved\" when stock.json has enough of every line, otherwise \"not enough <sku>\" for the first line that is short. In reserve-order, ask the stock service with request-reply, keep the order as the body, and log \"Stock service answered for ${header.orderId}: <the answer>\".", "check": {"log_regex": ["Stock service answered for ORD-1001: reserved", "Stock service answered for ORD-1003: not enough CAMEL-CAP"]}, "reference": {JR: jr_s3}},
