配置Mule代理API使用域共享监听器时遇错误求助

问题详情 #

创建Mule API代理发布内部API，代理需使用HTTPS协议的共享监听器。启动代理时，Mule引擎抛出以下错误：

+ org.mule.runtime.deployment.model.api.DeploymentInitException:               +
+ PropertyNotFoundException: Couldn't find configuration property value for    +
+ key ${inbound.keystore.password} from properties provider environment        +
+ properties provider - within resolver Deployment properties trying to        +
+ process key inbound.keystore.password - within resolver global-properties    +
+ configuration attributes trying to process key inbound.keystore.password -   +
+ within resolver environment properties provider trying to process key        +
+ inbound.keystore.password - within resolver Deployment properties trying to  +
+ process key inbound.keystore.password - within resolver                      +
+ configuration-attribute provider composed of (<configuration-properties      +
+ file="config.properties"> - file: http-proxy.xml, line number: 16) trying    +
+ to process key inbound.keystore.password - within resolver                   +
+ global-properties configuration attributes trying to process key             +
+ inbound.keystore.password - within resolver configuration-attribute          +
+ provider composed of (<configuration-properties file="config.properties"> -  +
+ file: http-proxy.xml, line number: 16) trying to process key                 +
+ inbound.keystore.password - within resolver environment properties provider  +
+ trying to process key inbound.keystore.password - within resolver            +
+ Deployment properties trying to process key inbound.keystore.password -      +
+ within resolver External files trying to process key                         +
+ inbound.keystore.password - within resolver Deployment properties trying to  +
+ process key inbound.keystore.password

当前状况：

• 在conf文件夹中找不到config.properties和http-proxy.xml文件
• 该共享端口已被引用此域的其他Mule应用成功使用，且域项目已发布至服务器

补充配置信息 #

域配置文件 #

<?xml version="1.0" encoding="UTF-8"?>
<domain:mule-domain
        xmlns:tls="http://www.mulesoft.org/schema/mule/tls"
        xmlns:http="http://www.mulesoft.org/schema/mule/http"
        xmlns="http://www.mulesoft.org/schema/mule/core"
        xmlns:domain="http://www.mulesoft.org/schema/mule/ee/domain"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xsi:schemaLocation="
               http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
               http://www.mulesoft.org/schema/mule/ee/domain http://www.mulesoft.org/schema/mule/ee/domain/current/mule-domain-ee.xsd
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
http://www.mulesoft.org/schema/mule/tls http://www.mulesoft.org/schema/mule/tls/current/mule-tls.xsd">
    <tls:context name="Domain_TLS_Context" doc:name="TLS Context" doc:id="some guid" >
        <tls:key-store type="pkcs12" path="mule.p12" keyPassword="***" password="***"/>
    </tls:context>
    <http:listener-config name="myShared1_Listener_config" doc:name="api.payshop.pt_Listener_config" doc:id="50d5570d-5491-4617-a8e6-caa699dbbcc6" >
        <http:listener-connection protocol="HTTPS" host="0.0.0.0" port="9443" tlsContext="Domain_TLS_Context" />
    </http:listener-config>
    <http:listener-config name="myShared2_Listener_config" doc:name="HTTP Listener config" doc:id="3e9c63c5-2f37-41fb-8743-c27bcf589b38" >
        <http:listener-connection protocol="HTTPS" host="0.0.0.0" port="9444" tlsContext="Domain_TLS_Context" />
    </http:listener-config>
    <!-- configure here resource to be shared within the domain -->
</domain:mule-domain>

代理API设置（API Manager页面） #

Downstream:
    Protocol: HTTPS
    Inbound TLS: Not defined (its defined in the domain project)
    Port: 9444
    Base Path:/test
    ... the rest has the defaults

解决线索 #

• 检查代理部署包内部：API Manager生成的代理项目可能将http-proxy.xml包含在部署包内部，而非conf文件夹。解压代理部署包查找该文件，确认是否存在${inbound.keystore.password}的引用。
• 验证代理与域的关联：确认API代理是否正确关联到目标域，避免代理尝试自行加载TLS配置，而非使用域的共享监听器配置。
• 排查属性依赖来源：检查服务器环境变量或部署属性中是否存在inbound.keystore.password，若代理误引入该属性依赖，需注入对应值或移除不必要的属性引用。
• 重新生成代理：若API Manager生成代理时错误添加了独立TLS配置，可尝试重新生成代理，确保设置中明确指定使用域的共享监听器。
• 确认域部署完整性：检查域项目的部署目录中是否存在mule.p12证书文件，避免因域资源缺失导致代理加载配置失败。

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