Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:
Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.
AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a . If my response doesn’t make sense for your topic, please react to it with a
.
Looking at the documentation and community discussions, I can provide information about consuming messages from a queue using CocoaMQTT in a Swift application.
The Solace documentation and community discussions indicate that:
-
For MQTT connections to Solace event broker:
- Port 8883 is used for MQTT over SSL/TLS
- Port 8443 is used for MQTT over WebSocket Secure (WSS)
-
CocoaMQTT library can be used to establish MQTT connections, with successful connections reported using port 8883 for SSL/MQTT.
Here’s a summary of the key points for implementation:
- Use the appropriate connection URL and port (8883 for SSL or 8443 for WSS)
- Configure SSL/TLS settings if using secure connections
- MQTT v5.0 is recommended over MQTT 3.1.1 for better features and interoperability
Relevant sources:
- Issue with Establishing MQTT Connections
- iOS Simulator-Compatible Libraries
- Consuming Messages from a Queue
Note: The Solace iOS SDK is no longer supported, and it’s recommended to use MQTT libraries like CocoaMQTT instead.