Troubleshooting ServiceNow Connector 6.16 - Mule 4

To troubleshoot Anypoint Connector for ServiceNow (ServiceNow Connector), become familiar with the information about interpreting commonly thrown exception messages.

Enable Verbose Exception Logging

Enable verbose exception logs to show a complete stack trace of the error instead of the default truncated output:

In Studio, right-click on the project and select Run > Run Configurations.
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 ServiceNow 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:

Access Anypoint Studio and navigate to the Package Explorer view.
Open your application’s project name.
Open the src/main/resources folder.
Open the log4j2.xml file inside the folder.

Add an <AsyncLogger> tag inside the <Loggers> tag:

			<Loggers>
				...
				<AsyncLogger name="com.mulesoft.connectors.servicenow" level="DEBUG"/>
				...
			</Loggers>

Save your application changes.
Click the project name in Package Explorer and then click Run > Run As > Mule Application.

Understand Commonly Thrown Exceptions

Here is a list of commonly thrown exception messages and how to interpret them:

SERVICENOW:BAD_REQUEST

The request is incorrect, for example, there are invalid input headers or the service does not exist.

SERVICENOW:CANNOT_DISPATCH

An error occurs when sending the request.

SERVICENOW:CONNECTIVITY

Either a connection could not be established or there is a connectivity error.

SERVICENOW:ENCODING

There is an encoding error when parsing the request or the response.

SERVICENOW:INVALID_WSDL
```
The WSDL is invalid or inconsistent.
```

SERVICENOW:PROCESSING_ERROR

There is a processing error, for example, there is an interruption during initialization.

SERVICENOW:RETRY_EXHAUSTED

The maximum number of retries for the operation is reached.

SERVICENOW:SOAP_FAULT
```
There is a SOAP fault error.
```

SERVICENOW:TIMEOUT

A specific request takes longer than the configuration timeout values.

Troubleshooting ServiceNow Connector 6.16 - Mule 4

Enable Verbose Exception Logging

Enable Verbose Logging

Understand Commonly Thrown Exceptions

See Also