调用函数前如何初始化Ballerina模块？WSO2 MI部署异常排查

在WSO2 MI中使用自定义Ballerina模块时遇到如下错误：

[2025-07-29 16:07:19,538] ERROR {io.ballerina.stdlib.mi.Mediator} - {api:BallerinLinuxAPI} function 'helloWorld' is called before module initialization

开发的Ballerina模块代码如下：

import wso2/mi;
import ballerina/log;
import ballerina/io;

@mi:Operation {}
public function helloWorld(string entry)returns json {
    log:printInfo("Entry: " + entry);
    return {"text" : entry};
}

public function main() {
    io:println("Hello, World!");
}

WSO2 MI项目是一个API，通过POST请求接收字符串输入并调用上述helloWorld函数，代码如下：

<?xml version="1.0" encoding="UTF-8"?>
<api xmlns="http://ws.apache.org/ns/synapse" name="BallerinLinuxAPI" context="/ballerinalinux">
    <resource methods="POST" uri-template="/">
        <inSequence>
            <BalHelloWorld.helloWorld>
                <responseVariable>BalHelloWorld_helloWorld_1</responseVariable>
                <overwriteBody>false</overwriteBody>
                <entry>{${payload}}</entry>
            </BalHelloWorld.helloWorld>
            <!-- Extract the input string from the request -->
            <!-- Log the input -->
            <!-- Call the Ballerina module function using script mediator -->
            <!-- Create JSON response -->
            <payloadFactory media-type="json">
                <format>
                    {
                    "result": "${vars.processedString}",
                    "status": "success",
                    "message": "String processed successfully"
                    }
                </format>
            </payloadFactory>
            
            <respond/>
        </inSequence>
        <faultSequence>
            <log category="ERROR">
                <message>Error processing request: ${props.synapse.ERROR_MESSAGE}</message>
            </log>
            <payloadFactory media-type="json">
                <format>
                    {
                    "error": "Processing failed",
                    "message": "${props.synapse.ERROR_MESSAGE}"
                    }
                </format>
            </payloadFactory>
            <respond/>
        </faultSequence>
    </resource>
</api>

该模块在Windows环境下通过VS Code的“Try it”功能测试正常，但在Debian 12环境中部署无报错（部署日志如下），调用时却出现上述错误：

[2025-07-29 16:06:48,491]  INFO {org.apache.synapse.deployers.LibraryArtifactDeployer} - Synapse Library named '{io.ballerina.stdlib.mi}BalHelloWorld' has been deployed from file : /usr/local/wso2mi-4.4.0/tmp/carbonapps/-1234/1753798008377balhellowrold_1.0.0.car/BalHelloWorld-connector_0.1.0/BalHelloWorld-connector-0.1.0.zip
[2025-07-29 16:06:48,492]  INFO {org.apache.synapse.config.xml.SynapseImportFactory} - Successfully created Synapse Import: BalHelloWorld
[2025-07-29 16:06:48,502]  WARN {org.apache.synapse.deployers.LibraryArtifactDeployer} - Hot deployment thread picked up an already deployed synapse library - Ignoring
[2025-07-29 16:06:48,526]  INFO {org.apache.synapse.api.API} - {api:BallerinLinuxAPI} Initializing API: BallerinLinuxAPI
[2025-07-29 16:06:48,527]  INFO {org.apache.synapse.deployers.APIDeployer} - API named 'BallerinLinuxAPI' has been deployed from file : /usr/local/wso2mi-4.4.0/tmp/carbonapps/-1234/1753798008377balhellowrold_1.0.0.car/BallerinLinuxAPI_1.0.0/BallerinLinuxAPI-1.0.0.xml
[2025-07-29 16:06:48,527]  INFO {org.wso2.micro.integrator.initializer.deployment.application.deployer.CappDeployer} - Successfully Deployed Carbon Application : balhellowrold_1.0.0{super-tenant}

预期helloWorld函数能正常执行并在日志中打印信息，请问问题出在哪里？如何在Linux环境下解决该问题？

问题原因 #

1. Ballerina模块的main函数干扰初始化流程：WSO2 MI集成Ballerina模块时，不需要main函数作为入口。Linux环境下MI的模块加载机制与VS Code测试环境不同，main函数会被当作模块初始化的一部分，但初始化未完成就被API调用触发，导致抛出"function called before module initialization"错误。VS Code的"Try it"是独立运行Ballerina程序，main函数可正常执行，但部署到MI后会打乱模块初始化逻辑。

2. API序列变量引用错误：API调用Ballerina函数后，结果存储在BalHelloWorld_helloWorld_1变量中，但后续payloadFactory引用的${vars.processedString}未被赋值，即使模块初始化正常，也会导致返回结果异常。

解决步骤 #

步骤1：移除Ballerina模块中的main函数 #

修改Ballerina代码，删除main函数，保留MI集成所需的带@mi:Operation注解的函数即可：

import wso2/mi;
import ballerina/log;

@mi:Operation {}
public function helloWorld(string entry)returns json {
    log:printInfo("Entry: " + entry);
    return {"text" : entry};
}

步骤2：修正API序列的变量引用逻辑 #

更新API的inSequence，将Ballerina函数的返回结果赋值给processedString变量，确保payloadFactory能正确引用：

<?xml version="1.0" encoding="UTF-8"?>
<api xmlns="http://ws.apache.org/ns/synapse" name="BallerinLinuxAPI" context="/ballerinalinux">
    <resource methods="POST" uri-template="/">
        <inSequence>
            <BalHelloWorld.helloWorld>
                <responseVariable>BalHelloWorld_helloWorld_1</responseVariable>
                <overwriteBody>false</overwriteBody>
                <entry>{$body}</entry>
            </BalHelloWorld.helloWorld>
            <!-- 将Ballerina返回的结果赋值给processedString变量 -->
            <property expression="$ctx:BalHelloWorld_helloWorld_1/text" name="processedString" scope="default" type="STRING"/>
            <!-- 使用变量生成响应 -->
            <payloadFactory media-type="json">
                <format>
                    {
                    "result": "$1",
                    "status": "success",
                    "message": "String processed successfully"
                    }
                </format>
                <args>
                    <arg evaluator="xml" expression="$ctx:processedString"/>
                </args>
            </payloadFactory>
            
            <respond/>
        </inSequence>
        <faultSequence>
            <log category="ERROR">
                <message>Error processing request: ${props.synapse.ERROR_MESSAGE}</message>
            </log>
            <payloadFactory media-type="json">
                <format>
                    {
                    "error": "Processing failed",
                    "message": "$1"
                    }
                </format>
                <args>
                    <arg evaluator="xml" expression="$ctx:ERROR_MESSAGE"/>
                </args>
            </payloadFactory>
            <respond/>
        </faultSequence>
    </resource>
</api>

步骤3：重新构建并部署 #

1. 在Ballerina项目目录执行bal build生成新的连接器包。
2. 重新打包Carbon Application（CAR文件），确保包含更新后的Ballerina模块和API配置。
3. 停止WSO2 MI，清理<MI_HOME>/tmp和<MI_HOME>/repository/deployment/server下的旧部署文件，重启MI后部署新的CAR包。

步骤4：验证结果 #

调用API的POST接口，检查MI日志是否打印Entry: [输入内容]，同时确认返回的JSON响应包含正确的result字段，即可确认问题已解决。

内容的提问来源于stack exchange，提问作者user31169131