Closed TomasTokaMrazek closed 3 years ago
It was related to additional dropins for Azure Service Bus. Looks like APIM 3.2.0 is not compatible with following settings.
https://ei.docs.wso2.com/en/latest/micro-integrator/setup/brokers/configure-with-azureservicebus/
Description:
When I try to create user, I'll get the following error in title. It appears related to some wrong usage of internal broker.
I haven't touch any of the related configurations in deployment.toml, the one thing I did was change primary key in keystore, add CA to truststore and change hostname in deployment.toml to FQDN.
It's not an internal firewall issue, as I am capable of connecting to the broker via curl.
Here's wso2carbon.log from startup:
I don't understand, how in one line there's successful connection to throttleData topic
TID: [-1] [] [2021-06-30 02:11:42,786] INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Connection attempt: 1 for JMS Provider for listener: Siddhi-JMS-Consumer#throttleData was successful!
Second line says that topic was not found
TID: [-1] [] [2021-06-30 02:11:43,843] WARN {org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils} - Cannot locate destination : throttleData
Third line says that, the connection wasn't in fact successful
TID: [-1] [] [2021-06-30 02:11:45,811] WARN {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Polling tasks on destination : notification of type topic for listener Siddhi-JMS-Consumer#notification have not yet started after 3 seconds ..
And finally, during a restart procedure, there's a storm of errors related to JMS.
Steps to reproduce:
Install WSO2 APIM 3.2.0 Run Create user in Carbon console
Affected Product Version:
APIM 3.2.0
Environment details (with versions):