Solace Community is getting a facelift!
On March 3rd we will be starting the process of migrating Solace Community to a new platform. As a result, Solace Community will go in to a temporary read-only state. You will still be able to come onto Solace Community and search through posts to find answers, but you won't be able to ask questions, post comments, or react in any way.
We hope to have the migration complete by Wednesday March 5th (or sooner), so please keep an eye out!
Client Discunnect Automatically.
Hi Team,
We are using Solace hardware Appliance, but one of my client has been automatically disconnected, when I check log it is showing permission denied.
Comments
-
In log it is showing CLIENT_CLIENT_DISCUNNECT and permission denied.
0 -
@Muddam_Pullaiah
It looks like consumer client got disconnect when it try to bind queue or topic-endpoint. You have to check the "Owner" and "All other permission" of the endpoint.Owner: Assign the client-username which will be used by consumer application. The client who binds the queue through that username will have full permission. It can add or remove topic subscriptions to queue.
All other Permission: As the name says, you can define the permission level for all other client-usernames apart from the owner. Any client connects through another username will have that permission. I recommend to have "no-access" if the owner is assigned for the queue otherwise, you can have "consume" or "modify" permission.
Share the complete event error log if possible.
0
Categories
