You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, jndi-cp.properties.j2 file is referring only the apim.event_hub.username as the username to construct the TopicConnectionFactory when some conditions are true. This will break the configuration if email user is enabled in the deployment.toml and also when event_hub configurations are applied(TM seperation use case)
It will result constructing the endpoint setting the username as admin@[email protected]
Ideally this value should be admin!wso2.com!carbon.super to be success with the configurations.
Hence we need to refer apim.throttling.jms.username instead.
Steps to reproduce:
Configure APIM-4.0.0 with email-user enabled configs
Apply event_hub configurations.
Start the server and check jndi-cp.properties file.
Affected Product Version:
APIM-4.0.0
Environment details (with versions):
N/A
The text was updated successfully, but these errors were encountered:
Description:
Currently, jndi-cp.properties.j2 file is referring only the apim.event_hub.username as the username to construct the TopicConnectionFactory when some conditions are true. This will break the configuration if email user is enabled in the deployment.toml and also when event_hub configurations are applied(TM seperation use case)
It will result constructing the endpoint setting the username as admin@[email protected]
Ideally this value should be admin!wso2.com!carbon.super to be success with the configurations.
Hence we need to refer apim.throttling.jms.username instead.
Steps to reproduce:
Affected Product Version:
APIM-4.0.0
Environment details (with versions):
N/A
The text was updated successfully, but these errors were encountered: