--- schema_version: "1" id: ba5183aaefc2b26519ca3922114329a3b658d17707d01c6b213abac3fe0421ea title: Troubleshooting Amazon SQS Connector 5.12 collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/amazon-sqs-connector/latest/amazon-sqs-connector-troubleshooting.md canonical_url: https://docs.mulesoft.com/amazon-sqs-connector/latest/amazon-sqs-connector-troubleshooting source_site: docs.mulesoft.com content_type: documentation content_hash: 1c92725c5000ec5223ede6a98f417467345a189802913b6733b7eaec577fca1c description: MuleSoft Documentation Site release: "5.12" latest: true --- --- product: Amazon SQS Connector version: 5.12 is-latest-version: true --- # Troubleshooting Amazon SQS Connector 5.12 > For the full documentation index, see: https://docs.mulesoft.com/llms.txt To troubleshoot Anypoint Connector for Amazon SQS (Amazon SQS Connector), become familiar with the information about interpreting commonly thrown exception messages. ## Enable SSL Logging Enable SSL logs to investigate an issue related to TLS communications. Set your SSL log level depending on your required level of detail: 1. Enable only SSL log details: `javax.net.debug=ssl` 2. Enable only handshaking details. (The handshake protocol is a series of messages exchanged over the record protocol.) `javax.net.debug=ssl:handshake` 3. Enable handshaking details and SSL details at the same time: `javax.net.debug=ssl, handshake` 4. Enable the dumping of all details and traffic data: `javax.net.debug=all` > [!NOTE] This option is very verbose and under normal circumstances is not necessary. > [!WARNING] SSL logging results in a performance impact for HTTPS or other TLS connections. Enable > SSL logging only to troubleshoot a specific issue and do not enable it for extended periods. SSL > logging produces a significant amount of log messages and can inundate your log file if it is left > enabled and unattended. To enable SSL logs: Set the debug parameter as an argument in the runtime configuration for the application. 1. In Studio, right-click on the project and select **Run > Run Configurations**. 2. Go to the **Arguments** tab and add `-M-Djavax.net.debug=ssl` in the **VM arguments** section. ## Enable Verbose Exception Logging Enable verbose exception logs to show a complete stack trace of the error instead of the default truncated output: 1. In Studio, right-click on the project and select **Run > Run Configurations**. 2. Go to the **Arguments** tab and append the arguments in the **VM arguments** section to add the `mule.verbose.exceptions` property. For example: `-XX:PermSize=128M -XX:MaxPermSize=256M -Dmule.verbose.exceptions=true` ## Enable Verbose Logging To get a better understanding of why an application’s interaction with Amazon SQS Connector is failing, temporarily enable verbose logging for the connector. Remember to always disable enhanced verbosity after troubleshooting, because it can affect your Mule application’s performance. To enable verbose logging in the configuration file: 1. Access Anypoint Studio and navigate to the **Package Explorer** view. 2. Open your application’s project name. 3. Open the `src/main/resources` folder. 4. Open the `log4j2.xml` file inside the folder. 5. Add an `` tag inside the `` tag: ```xml ... ... ``` 6. Save your application changes. 7. Click the project name in **Package Explorer** and then click **Run** > **Run As** > **Mule Application**. ## Troubleshoot AWS STS Regionalized Endpoints In AWS SDK v2, the endpoint that the STS client of the `AssumeRoleConnectionProvider` uses to get session tokens is now regionalized instead of global. See the [AWS STS Regionalized endpoints](https://docs.aws.amazon.com/sdkref/latest/guide/feature-sts-regionalized-endpoints.html) documentation for details. As explained in the [AWS Security Token Service endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/sts.html) documentation, regionalized endpoints shouldn’t cause changes in the connector’s functionality. AWS recommends using Regional STS endpoints to reduce latency, build in redundancy, and increase session token validation. If you encounter any issues as a result of the change in endpoints to regionalized, you can force Amazon SQS Connector to use the global endpoint by specifying the URL endpoint `https://sts.amazonaws.com` in the **Custom STS Endpoint** field located in the **Advanced** tab of the **Global Elements** properties configuration window of the connector. ## Understand Commonly Thrown Exceptions Here is a list of commonly thrown exception messages and how to interpret them: - SQS:ACCESS\_DENIED The user does not have permission to execute this operation. - SQS:CONNECTIVITY The connection to the Amazon SQS server is interrupted. - SQS:INTERNAL\_FAILURE The request fails due to an unknown error, exception, or failure. - SQS:INVALID\_CREDENTIALS Authentication against the Amazon SQS server fails due to invalid credentials. - SQS:INVALID\_DATA The test connection cannot be performed because the Test Queue ARN parameter is not set. - SQS:MESSAGE\_NOT\_IN\_FLIGHT The specified message is not in flight. - SQS:MESSAGE\_SIZE\_THRESHOLD\_OUT\_OF\_RANGE The message threshold size is not between 0 and 256 KB. - SQS:OPT\_IN\_REQUIRED The AWS access key ID requires a subscription for the service. - SQS:OVER\_LIMIT The attempted action exceeds a limit, for example, if the Recieve Messages source receives the maximum number of inflight messages or if the Add Permission operation reaches the maximum number of permissions for the queue. - SQS:PARAMETER\_OUT\_RANGE The value is not within the specified range. - SQS:PURGE\_QUEUE\_IN\_PROGRESS The specified queue receives a Purge Queue request within the last 60 seconds. - SQS:QUEUE\_ALREADY\_EXISTS There is a queue with this name already and the request includes different attributes from the existing queue with this name. - SQS:QUEUE\_DELETED\_RECENTLY A queue with the same name is deleted within the last 60 seconds. - SQS:REQUEST\_EXPIRED The request reaches the service more than 15 minutes after the request date stamp or the request expiration date, or the request date stamp is more than 15 minutes in the future. - SQS:RETRY\_EXHAUSTED The retries of a certain execution block are exhausted. - SQS:S3\_BUCKET\_ACCESS\_DENIED The server returns an AmazonSQSException with a 403 HTTP status code. - SQS:S3\_BUCKET\_NOT\_FOUND The server returns an AmazonSQSException with a 404 HTTP status code. - SQS:SERVICE\_UNAVAILABLE The server is experiencing a temporary failure. - SQS:THROTTLING\_EXCEPTION The request fails due to request throttling. ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Amazon SQS Connector Reference](https://docs.mulesoft.com/amazon-sqs-connector/latest/amazon-sqs-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues)