Websocket connection failed issue

SSL Connection: When you include ssl:// in the server URL, you receive a connection failure. This suggests that your WebSocket connection is using SSL/TLS encryption. Make sure that the ActiveMQ broker on AWS is configured to support SSL/TLS connections and that the necessary certificates are set up correctly. Additionally, ensure that your Spring Boot application is configured with the appropriate truststore and keystore files for SSL/TLS communication.

Port and Protocol: The default port for the ActiveMQ broker is 61616 for non-SSL connections and 61617 for SSL connections. Double-check that you are using the correct port for your setup. If you are using SSL, verify that your ActiveMQ broker is configured to listen on port 61617 for SSL connections.

Network Access: Confirm that the necessary network access is configured to allow connections between your Spring Boot application and the ActiveMQ broker on AWS. Ensure that any firewalls or security groups are properly configured to allow traffic on the relevant ports.

Credentials: Double-check that the username and password you are providing in the WebSocket configuration are correct and have the necessary permissions to establish a connection to the ActiveMQ broker.

ActiveMQ Configuration: Verify that the ActiveMQ broker on AWS is properly configured to accept WebSocket connections and that it is running and accessible. Check the ActiveMQ logs for any errors or warnings that could provide additional information about the connection issues.

AWS Configuration: Ensure that you have set up the necessary AWS credentials and permissions for your Spring Boot application to connect to the ActiveMQ broker. Check that the IAM user or role associated with your application has the required permissions to access the broker.