Hi again @Velu … ok, so I think the confusion here is that you’re looking at an “internal use only” client that the broker maintains whenever a Message VPN is enabled. #client is not your client connection. It is for the broker’s own internal communication. That’s why you’re seeing a weird port. Note the uptime is 41 days! ?
As mentioned in my first response, ignore anything that starts with # as they are all for internal stuff. Check this post: What are these objects that start with "#" ?? — Solace Community
So, what you need to do to get connected to your broker:
- in your Message VPN, create a new client-username to use. Configure however you want for authentication. Maybe “basic none” is the best way to start.
- If you’ve made a new client-profile for your client-username, and you want to use Guaranteed messaging, please make sure you enable a bunch of message spool settings in that profile
- If you’ve made a new acl-profile for your client-username, you’ll need to change the default behaviour of everything to “allow”. It is set to disallow by default.
- Easier to just use the
defaultacl-profile
- Easier to just use the
- Finally, as a test, make sure you can connect to the broker with just a regular Solace (SMF) client to make sure your username/password/whatever is working. Either SdkPerf, or the PubSub+ Manager “TryMe!” test applications.
Hope that helps!