Closed mcvidanagama closed 5 years ago
Error stack trace
TID: [-1234] [] [2019-05-28 10:38:57,793] ERROR {org.wso2.andes.server.registry.ApplicationRegistry} - org.wso2.andes.kernel.AndesException: Couldn't look up jndi entry for "WSO2MBStoreDB" {org.wso2.andes.server.registry.ApplicationRegistry}
TID: [-1234] [] [2019-05-28 10:38:57,794] ERROR {org.wso2.andes.server.Main} - Exception during startup. Triggering shutdown {org.wso2.andes.server.Main}
org.wso2.andes.kernel.AndesException: Unable to initialise application registry
at org.wso2.andes.server.Broker.startupImpl(Broker.java:311)
at org.wso2.andes.server.Broker.startup(Broker.java:110)
at org.wso2.andes.server.Main.startBroker(Main.java:217)
at org.wso2.andes.server.Main.execute(Main.java:206)
at org.wso2.andes.server.Main.
Even though we are not using MB store DB in Gateway, during the server startup, when the broker component tries to initialize, it looks for the MB store DB. Hence we need to keep the default H2 configuration as it is in master-datasource.xml. Need to update the documentation.
Tracking the documentation issue in https://github.com/wso2/product-apim/issues/5042.
Description: Even when the node is started as gateway worker[1], it looks for mb store db at startup. If we havent added mbstore in any of the datasources files the startup fails.
Suggested Labels: APIM, 260,gateway_profile Suggested Assignees: N/A Affected Product Version: 260 -wum updated up to date of creation of this issue OS, DB, other environment details and versions:
RHEL7, Puppet controlled deployment Steps to reproduce: Remove mb store db configs from datasources file. Start server with command[1]
[1] - ./bin/wso2server.sh --optimize -Dprofile=gateway-worker -DworkerNode=true start Related Issues: N/A