🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Cloud broker command logs
Hello @all,
i am browsing the command logs for the first time. I see a lot of log entries in the following pattern.
What is the problem regarding these log messages (no subscribe-topic exceptions fail-if-already-exists smf)?
The client has no problems subscribing to the queue and taking messages out of it.
Best regards
Jens
------------------------------------------------------------------------------------------------------------------------------------
Example:
2022-12-14T13:04:21.339+00:00 <local1.info> giga-production-wu8a0lf4cij-solace-primary-0 appuser[411]: SEMP2/mgmt 10.245.14.9 reddi-admin 13:04:21 13:04:21 ok (config
ure/acl-profile)# no subscribe-topic exceptions fail-if-already-exists smf list "*/rwws/mobile-config/export/>"
2022-12-14T13:04:22.747+00:00 <local1.info> giga-production-wu8a0lf4cij-solace-primary-0 appuser[411]: SEMP2/mgmt 10.245.14.6 reddi-admin 13:04:22 13:04:22 changed mode (config
ure)# acl-profile "export-nemo" message-vpn "reddi"
Answers
-
Hi @jesper,
I think what you're asking is why can a client's queue attract messages from topics that the ACL profile doesn't allow them to subscribe to?
If that is indeed your question it is b/c the queue itself has topic subscriptions which attract messages and then client-usernames with Consume (or higher) access can consume from it. The ACL profile disallowing topic subscriptions is only applied if the client-username is trying to subscribe directly to the topic without a queue.
If you meant to ask something else please clarify, but I hope that helps!
0
