MuleSoft errors
Common MuleSoft Anypoint errors, grouped by component. Open one for the exact error text, its likely causes, the fix and the official documentation.
- Errors
- 162
- Components
- 33
- Verified
- 156
- Official docs
- docs.mulesoft.com
162 errors in 33 groups
Anypoint Code Builder1
Anypoint MQ Connector1
APIkit for REST6
- APIKIT:BAD_REQUESTAPIKIT:BAD_REQUEST is the APIkit for REST error type that maps to HTTP status 400 with the response message "Bad request". APIkit validates incoming requests against your RAML or OAS API specification, so compare the failing request with the specification.
- APIKIT:METHOD_NOT_ALLOWEDAPIKIT:METHOD_NOT_ALLOWED is the APIkit for REST error type that maps to HTTP status 405 with the response message "Method not allowed". APIkit validates incoming requests against your RAML or OAS API specification, so compare the failing request with the specification.
- APIKIT:NOT_ACCEPTABLEAPIKIT:NOT_ACCEPTABLE is the APIkit for REST error type that maps to HTTP status 406 with the response message "Not acceptable". APIkit validates incoming requests against your RAML or OAS API specification, so compare the failing request with the specification.
- APIKIT:NOT_FOUNDAPIKIT:NOT_FOUND is the APIkit for REST error type that maps to HTTP status 404 with the response message "Resource not found". APIkit validates incoming requests against your RAML or OAS API specification, so compare the failing request with the specification.
- APIKIT:NOT_IMPLEMENTEDAPIKIT:NOT_IMPLEMENTED is the APIkit for REST error type that maps to HTTP status 501 with the response message "Not implemented". APIkit validates incoming requests against your RAML or OAS API specification, so compare the failing request with the specification.
- APIKIT:UNSUPPORTED_MEDIA_TYPEAPIKIT:UNSUPPORTED_MEDIA_TYPE is the APIkit for REST error type that maps to HTTP status 415 with the response message "Unsupported media type". APIkit validates incoming requests against your RAML or OAS API specification, so compare the failing request with the specification.
Basic Authentication: Simple policy1
Batch1
Client ID Enforcement policy1
CloudHub1
CloudHub 2.03
- 502 Bad Gateway during traffic switch to CloudHub 2.0A 502 Bad Gateway while switching traffic from CloudHub to CloudHub 2.0 usually means the dedicated load balancer cannot talk to the new app. Check that the upstream uses TLS 1.2 or higher and that the app's listener binds to 0.0.0.0.
- 504 Gateway Timeout during or after traffic switch to CloudHub 2.0A 504 Gateway Timeout during or after the traffic switch to CloudHub 2.0 means a request ran longer than the load balancer waits. Keep client timeouts under 300 seconds, or raise Read Response Timeout in the private space's Advanced settings.
- Runtime Version not supported for this target"Runtime Version not supported for this target" appears when deploying to CloudHub 2.0 with a Mule runtime it does not accept, such as Mule 4.3.0. Deploy on a supported LTS or Edge runtime and rebuild the JAR.
Database Connector12
- Could not obtain connection from data sourceCould not obtain connection from data source appears when a Mule app with a CloudHub static IP runs its database connectivity test at deployment before the static IP is assigned. Set the system property -DdoTestConnectivity=false.
- DB:BAD_SQL_SYNTAXDB:BAD_SQL_SYNTAX means the SQL query you gave Database Connector contains invalid syntax. Correct the statement for your database, and check any part of it that is built dynamically.
- DB:CANNOT_LOAD_DRIVERDB:CANNOT_LOAD_DRIVER means Database Connector cannot load the JDBC driver for the connection. Make sure the driver for your database is available to the application.
- DB:CANNOT_REACHDB:CANNOT_REACH means Database Connector cannot establish a connection with the RDBMS. Check the host and port in the Database configuration and the network path from the app to the database server.
- DB:CONNECTIVITYDB:CONNECTIVITY covers several possible connection problems in Database Connector, including a poorly configured connection, no response from the database and a lost connection. Check the connection configuration first, then add a reconnection strategy.
- DB:INVALID_CREDENTIALSDB:INVALID_CREDENTIALS means the database rejected the user name or password that Database Connector provided. Correct the credentials in the Database configuration for this environment.
- DB:INVALID_DATABASEDB:INVALID_DATABASE means the connection to the RDBMS was established but the database named in the configuration does not exist. Correct the database name.
- DB:QUERY_EXECUTIONDB:QUERY_EXECUTION means the database accepted the connection but the execution of the query failed. Turn on verbose logging for Database Connector to see the database's own message, then fix the query, its parameters or its timeout.
- DB:RETRY_EXHAUSTEDDB:RETRY_EXHAUSTED means all reconnection attempts of a Database Connector operation failed. Fix the connection problem behind the attempts, and review the reconnection strategy.
- Inconsistency!!! Statement culled from deathmarchThis C3P0 error appears in Database Connector under high concurrency. The documented workaround is to set preparedStatementCacheSize to 0 on the pooling profile and set an Oracle JDBC statement cache size.
- Unsupported feature 'call'Snowflake returns Unsupported feature 'call' when a callable statement in Database Connector is written with curly brackets. Write the statement without them, for example call doubleMyInt(:myInt).
- XML-24509: Duplicated definitionXML-24509 Duplicated definition is an XML parsing error that appears when a Mule app uses Oracle XML extensions with Database Connector. Add xmlparserv2.jar as a plugin dependency, or point the JAXP factories at the Xerces implementation.
DataWeave7
- Cannot coerce String to DateThis DataWeave error means a String could not be converted to a Date because the text is not a valid date for the format and parsing mode in use. Correct the input value, or pick a parsing mode that fits how strict you need to be.
- Cannot open a new cursor on a closed streamCannot open a new cursor on a closed stream means a stream was closed before DataWeave could read it. The docs state there is no workaround, so find the component that closes the stream and report the case to MuleSoft support.
- No space left on deviceNo space left on device in a DataWeave transformation means the temporary files DataWeave writes for large payloads filled the disk. Give the application more resources, or reduce how much it buffers at once.
- Stack Overflow. Max stack is 256Stack Overflow. Max stack is 256 means a DataWeave function recursed deeper than the stack limit allows. Rewrite the recursion so it goes less deep, or raise the limit with the com.mulesoft.dw.stacksize property.
- Text plain writer is unable to write ArrayText plain writer is unable to write Array means the script has no output format, so DataWeave inferred plain text and cannot write the array the script returns. Declare an output format that supports arrays.
- Trying to output non-whitespace characters outside main element treeThis DataWeave error means the script's output was inferred as XML, but the value it returns is not a valid XML document. Declare the output format you really want, for example output text/plain.
- You called the function '++' with these argumentsThis DataWeave error means a function was called with a kind of argument it does not accept, most often null. Find which argument is Null in the list the message prints, then give it a fallback with the default operator.
Email Connector12
- EMAIL:ACCESSING_FOLDEREMAIL:ACCESSING_FOLDER means there was a problem accessing an email folder, or the folder does not exist. Check the folder name the operation uses against the mailbox.
- EMAIL:ATTACHMENTEMAIL:ATTACHMENT means an error occurred while trying to send an attachment. Check the attachment content and type that the Send operation receives.
- EMAIL:AUTHENTICATIONEMAIL:AUTHENTICATION means authentication against the mail server failed. For Gmail with two-factor authentication, use an app-specific password instead of the account password.
- EMAIL:CONNECTION_TIMEOUTEMAIL:CONNECTION_TIMEOUT means the mail server took too long to reply to a data request. Check the server and network before raising timeouts on the connection.
- EMAIL:CONNECTIVITYEMAIL:CONNECTIVITY means a connection to the mail server could not be established. Check the host, port and TLS settings on the connection, then read the JavaMail debug output.
- EMAIL:DISCONNECTEDEMAIL:DISCONNECTED means an error occurred while connecting to the mail store, or the connection was interrupted. Read the JavaMail debug output to see where the session dropped.
- EMAIL:EMAIL_NOT_FOUNDEMAIL:EMAIL_NOT_FOUND means the email identified by emailId cannot be found in the mailbox folder. Check the ID and the folder, since the email may have been moved or deleted.
- EMAIL:INVALID_CREDENTIALSEMAIL:INVALID_CREDENTIALS means the username and password parameter consistency check failed. Check that the user and password on the connection are both set correctly.
- EMAIL:READ_EMAILEMAIL:READ_EMAIL means an error occurred while reading the content of an email. Use the JavaMail debug output to find the message that fails, and check the Jakarta Mail MIME properties if the message is malformed.
- EMAIL:SENDEMAIL:SEND means an exception occurred while trying to send an email. Read the SMTP debug output to see the server's reply.
- EMAIL:SSL_ERROREMAIL:SSL_ERROR means the SSL context could not be created, or the TLS context is not configured properly. Review the TLS context on the secure email connection.
- EMAIL:UNKNOWN_HOSTEMAIL:UNKNOWN_HOST means the IP address of the mail host cannot be determined, or the port is out of range. Fix the host name or port in the connection configuration.
File Connector7
- FILE:ACCESS_DENIEDFILE:ACCESS_DENIED means a File Connector operation tried an action on a file or path that the user running the app is not permitted to perform. Grant that user the permission on the path.
- FILE:CONNECTIVITYFILE:CONNECTIVITY means the connection to the file server is no longer valid. Apply a reconnection strategy, and check that the file system the app uses is still available.
- FILE:FILE_ALREADY_EXISTSFILE:FILE_ALREADY_EXISTS means the target file already exists and the operation is not allowed to overwrite it. Set Overwrite to true, pick a different write mode, or use a unique file name.
- FILE:FILE_LOCKFILE:FILE_LOCK means File Connector tried to lock a file and could not. Another process or flow is holding the file, so release that lock or read without locking.
- FILE:ILLEGAL_CONTENTFILE:ILLEGAL_CONTENT means the File Connector Write operation received content it cannot write. Check the expression in the operation's content, and make sure it produces writable data.
- FILE:ILLEGAL_PATHFILE:ILLEGAL_PATH means a File Connector operation was given a path that does not exist while Create parent directories is set to false. Correct the path, or let the operation create the missing directories.
- java.lang.OutOfMemoryError when listing filesA java.lang.OutOfMemoryError from the File Connector List operation with large files is caused by the default streaming strategy, Repeatable file store iterable. Change the operation's Streaming strategy to No repeatable iterable.
FTP Connector3
- FTP:ACCESS_DENIEDFTP:ACCESS_DENIED means the operation tried to do something on an FTP path that the connected user has no permission for. Grant the permission on the server or connect as a user that has it.
- FTP:CONNECTIVITYFTP:CONNECTIVITY means the connection to the FTP server was interrupted. Check the server and network, then reproduce with an FTP client to see whether the problem is outside Mule.
- FTP:ILLEGAL_PATHFTP:ILLEGAL_PATH means the path given to the FTP operation is invalid, for example because it does not exist. Correct the path or create the directory on the server.
HTTP Connector20
- HTTP:BAD_GATEWAYHTTP:BAD_GATEWAY means a server acting as a gateway or proxy received an invalid response while handling your request (HTTP 502). The fault is behind that gateway, so check the upstream service and retry.
- HTTP:BAD_REQUESTHTTP:BAD_REQUEST means the server could not understand the request the HTTP Request operation sent because its syntax was invalid (HTTP 400). Log the outgoing request, compare it with what the server expects, and correct the body, headers or parameters.
- HTTP:BASIC_AUTHENTICATIONHTTP:BASIC_AUTHENTICATION means a request did not carry basic authentication, or carried the wrong credentials. Send a valid basic authentication header with the request.
- HTTP:CLIENT_SECURITYHTTP:CLIENT_SECURITY means a security problem enforced by an external entity occurred during an HTTP request. Look at the more specific error, such as HTTP:UNAUTHORIZED, and fix the credentials or permissions the external system rejected.
- HTTP:CONNECTIVITYHTTP:CONNECTIVITY means the HTTP Request operation could not establish a connection to the server. Check the host, port, protocol and TLS settings, and add your own retry because the operation does not use the reconnection strategy for retries.
- HTTP:FORBIDDENHTTP:FORBIDDEN means the server refused to return the resource because the client does not have access rights to it (HTTP 403). The credentials were sent, so fix the permissions of the identity behind them on the target system.
- HTTP:GATEWAY_TIMEOUTHTTP:GATEWAY_TIMEOUT means a server acting as a gateway or proxy did not receive a response from its upstream within the specified time (HTTP 504). The timeout happened behind the gateway, not in your Mule app's own Response Timeout.
- HTTP:INTERNAL_SERVER_ERRORHTTP:INTERNAL_SERVER_ERROR means the server hit a situation that prevented it from fulfilling the request the HTTP Request operation sent (HTTP 500). Read the response body and the remote system's logs to find what failed there.
- HTTP:METHOD_NOT_ALLOWEDHTTP:METHOD_NOT_ALLOWED means the server does not support the request method for the target resource (HTTP 405). Change the method on the HTTP Request operation to one the resource accepts.
- HTTP:NOT_ACCEPTABLEHTTP:NOT_ACCEPTABLE means the server cannot produce a response that matches the content negotiation headers of the request (HTTP 406). Correct the Accept headers the HTTP Request operation sends.
- HTTP:NOT_FOUNDHTTP:NOT_FOUND means the HTTP Request operation received a 404 response because the server could not find the requested resource. Check the URL shown in the error description, then correct the request or handle the error type in an error handler.
- HTTP:RETRY_EXHAUSTEDHTTP:RETRY_EXHAUSTED means the maximum number of retries for the HTTP operation was reached. Fix the failure that each attempt hits, which is usually a connectivity problem with the remote host.
- HTTP:SECURITYHTTP:SECURITY means the authentication of the HTTP requester failed. Check the authentication settings and credentials on the HTTP Request configuration.
- HTTP:SERVICE_UNAVAILABLEHTTP:SERVICE_UNAVAILABLE means the server could not handle the request because it is down for maintenance or overloaded (HTTP 503). The fault is on the remote side, so retry after a delay and handle the error if the service stays down.
- HTTP:TIMEOUTHTTP:TIMEOUT means a request sent by the HTTP Request operation timed out before the response arrived. The wait is set by Response Timeout, which is 10000 milliseconds unless you change it, so raise it or make the remote service answer faster.
- HTTP:TOO_MANY_REQUESTSHTTP:TOO_MANY_REQUESTS means the server received too many requests from your app in a given amount of time (HTTP 429). Send fewer calls at once and retry after a delay.
- HTTP:UNAUTHORIZEDHTTP:UNAUTHORIZED means the server rejected the HTTP Request operation because authentication failed or was not provided (HTTP 401). Send the credentials the server expects, and handle the error type if a rejected call is something the flow should survive.
- HTTP:UNSUPPORTED_MEDIA_TYPEHTTP:UNSUPPORTED_MEDIA_TYPE means the server does not support the media format of the data the HTTP Request operation sent (HTTP 415). Send the body in a format the server accepts and set the matching Content-Type.
- No access token foundNo access token found means an HTTP request with OAuth 2.0 authentication ran before any access token had been obtained. Call the authorization URL at least once first, or store the token and refresh it.
- Remotely closedA Remotely closed error means the HTTP connector reused a pooled connection that the remote system had already closed. Set Connection Idle Timeout on the HTTP Request configuration lower than the remote system's idle timeout, for example 10000 to 12000 milliseconds.
IBM MQ Connector4
- IBM-MQ:CONNECTIVITYIBM-MQ:CONNECTIVITY means the IBM MQ connection is no longer valid, and the connector disposes of it. Check the queue manager, configure reconnection, and give the listener its own configuration so a failed Publish or Consume cannot hang it.
- IBM-MQ:CONSUMINGIBM-MQ:CONSUMING means an error occurred while consuming messages, and it can simply mean no message was pending. If the app has stopped consuming, look for a backlog of unacknowledged messages.
- IBM-MQ:DESTINATION_NOT_FOUNDIBM-MQ:DESTINATION_NOT_FOUND means IBM MQ Connector could not find or create the destination. Check the queue or topic name against what exists on the queue manager.
- IBM-MQ:TIMEOUTIBM-MQ:TIMEOUT means the timeout for the requested IBM MQ operation was exceeded. Check why no message or reply arrived in time before raising the timeout.
IP Allowlist policy1
JMS Connector10
- JMS:ACKJMS:ACK means an error happened while acknowledging an in-flight message. Review the acknowledgment mode and make sure every path through the flow either acknowledges the message or recovers the session.
- JMS:CONNECTIVITYJMS:CONNECTIVITY means the JMS connection is no longer valid, and the connector disposes of it. Check the broker and configure a reconnection strategy so the app reconnects by itself.
- JMS:CONSUMINGJMS:CONSUMING means an error occurred while consuming messages, and it can simply mean no message was pending. If consumption has stopped altogether, look for a backlog of unacknowledged messages on the broker.
- JMS:DESTINATION_NOT_FOUNDJMS:DESTINATION_NOT_FOUND means JMS Connector could not find or create the queue or topic. Check the destination name and that the connecting user is allowed to use or create it on the broker.
- JMS:ILLEGAL_BODYJMS:ILLEGAL_BODY means the message body is invalid or cannot be converted to a supported type. Transform the payload into a type the connector can publish before the Publish operation.
- JMS:PUBLISHINGJMS:PUBLISHING means there was an error while publishing to the target queue or topic. Check the destination and the broker, then read the underlying cause with verbose logging on.
- JMS:RETRY_EXHAUSTEDJMS:RETRY_EXHAUSTED means the maximum number of retries for the JMS operation was reached. Find the error each attempt hit, which is logged before this one, and fix that.
- JMS:SECURITYJMS:SECURITY means the JMS operation failed because of a security-related error. Check the credentials in the JMS connection and what that user is allowed to do on the broker.
- JMS:TIMEOUTJMS:TIMEOUT means the timeout for the requested JMS operation was exceeded. Check why the broker or the replying party did not answer in time before raising the timeout.
- Session's XAResource has not been enlisted in a distributed transactionThis ActiveMQ error appears when an XA connection or session is used outside a transaction on ActiveMQ 5.16.x and later. Run the XA work inside a transaction, or add jms.xaAckMode=1 to the broker URL.
JSON Module1
JSON Threat Protection policy1
JWT Validation policy2
- 400 Token was not provided in the requestAn API protected by the JWT Validation policy returns 400 when the request carries no token where the policy looks for it. Send the JWT in the place the policy's JWT Origin and Token Expression settings name.
- 401 from the JWT Validation policyAn API protected by the JWT Validation policy returns 401 when the token's signature is invalid, a required claim is missing or fails validation, or the token cannot be parsed. Compare the token with the policy's signing method, key and claim settings.
Mule runtime8
- Flow is unable to accept new events at this timeThis message means the flow is under back-pressure: it cannot take more events from its source right now. Check the flow's maxConcurrency and how long each event takes to process.
- MULE:CONNECTIVITYMULE:CONNECTIVITY means there was a problem establishing a connection. It is the parent of connector errors such as DB:CONNECTIVITY and FTP:CONNECTIVITY, so find the connector named in the log and fix or retry its connection.
- MULE:EXPRESSIONMULE:EXPRESSION means an error occurred while Mule evaluated a DataWeave expression. Find the expression named in the log, check the values it reads for nulls or wrong types, and add a default or a handler.
- MULE:FATAL_JVM_ERRORMULE:FATAL_JVM_ERROR means a fatal error occurred in the JVM, such as a stack overflow. It cannot be handled in a flow, and the only safe recovery after a VirtualMachineError is to restart the Mule runtime instance.
- MULE:REDELIVERY_EXHAUSTEDMULE:REDELIVERY_EXHAUSTED means a source's maximum attempts to reprocess a message have been used up. Fix the error that makes the flow fail on that message, then review the Max Redelivery Count of the redelivery policy.
- MULE:STREAM_MAXIMUM_SIZE_EXCEEDEDMULE:STREAM_MAXIMUM_SIZE_EXCEEDED means a stream grew past the maximum size allowed for it, typically the in-memory buffer of a repeatable in-memory stream. Raise the buffer's maximum size, or use a streaming strategy that does not keep the content in memory.
- MULE:TIMEOUTMULE:TIMEOUT means a timeout occurred while Mule processed a message, for example a Scatter-Gather route that did not finish before the router's timeout. Speed up the slow route or raise the timeout.
- MULE:UNKNOWNMULE:UNKNOWN means an unknown or unexpected error occurred. It cannot be handled directly by its own type, only by a handler for ANY, so read the error description and cause in the log to find the real failure.
OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider policy2
- 400 Invalid tokenAn API protected by the OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider policy returns 400 when the access token is invalid. Request a new token from the provider and send that one.
- 403 Forbidden, invalid client application credentialsAn API protected by the OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider policy returns 403 when the client application credentials behind the token are invalid for this API. Use a token issued to a client application that has access to the API.
Object Store Connector3
- OS:KEY_ALREADY_EXISTSOS:KEY_ALREADY_EXISTS means an Object Store Store operation with Fail If Present set to true found the key already in the store. Leave Fail If Present at false to update the value, or handle the error when a duplicate is expected.
- OS:KEY_NOT_FOUNDOS:KEY_NOT_FOUND means an Object Store Retrieve or Remove operation asked for a key that has no value in the store. Check that the key exists first with Contains, or give Retrieve a default value.
- OS:NULL_VALUEOS:NULL_VALUE means an Object Store Store operation was given a null value while Fail On Null Value is true, which is the default. Give the value a fallback, or set Fail On Null Value to false to skip the operation.
Rate Limiting policy1
Rate Limiting: SLA-Based policy2
- 401 Request blocked due to invalid client credentials (Rate Limiting: SLA-Based)An API protected by the Rate Limiting: SLA-Based policy returns 401 when the client ID or client secret is invalid. A client with no contract with the API is always rejected, so create the contract in API Manager and send its credentials.
- 429 Quota exceeded (Rate Limiting: SLA-Based)An API protected by the Rate Limiting: SLA-Based policy returns 429 when the client application has used up the quota of its SLA tier for the current window. Wait for the window to finish, or move the client to a tier with a higher limit.
Salesforce Connector12
- SALESFORCE:COMMUNICATIONSALESFORCE:COMMUNICATION means a communication error occurred between the Mule app and Salesforce. Read the full exception to find which call failed and why.
- SALESFORCE:CONNECTIVITYSALESFORCE:CONNECTIVITY means a connection to Salesforce could not be established. Review the connector configuration and the reconnection strategy.
- SALESFORCE:INSUFFICIENT_PERMISSIONSSALESFORCE:INSUFFICIENT_PERMISSIONS means the permissions of the connected Salesforce user are not enough for the operation. Grant that user the missing permission in Salesforce, or connect with a user that has it.
- SALESFORCE:INVALID_INPUTSALESFORCE:INVALID_INPUT means the input data given to the Salesforce operation is not valid. Compare the payload with what the object accepts, field by field.
- SALESFORCE:INVALID_RESPONSESALESFORCE:INVALID_RESPONSE means the connector could not process the response from Salesforce. Capture the full exception to see what was returned.
- SALESFORCE:LIMIT_EXCEEDEDSALESFORCE:LIMIT_EXCEEDED means the operation went over a specific Salesforce limit. A documented example is creating more than 200 entities at once with the Create operation, so split the records into smaller batches.
- SALESFORCE:MUTUAL_AUTHENTICATION_FAILEDSALESFORCE:MUTUAL_AUTHENTICATION_FAILED means mutual TLS authentication with Salesforce failed. Check the certificate and key the connector presents, using SSL debug logging to see the handshake.
- SALESFORCE:NOT_FOUNDSALESFORCE:NOT_FOUND means Salesforce could not find the requested resource. Check the ID or name the operation sends.
- SALESFORCE:OPERATION_NOT_SUPPORTEDSALESFORCE:OPERATION_NOT_SUPPORTED means the operation is not supported for what it was asked to do. Use an operation that the target object or API supports.
- SALESFORCE:RETRY_EXHAUSTEDSALESFORCE:RETRY_EXHAUSTED means the maximum number of retries for the Salesforce operation was reached. Fix the error that each attempt hit, which is logged before this one.
- SALESFORCE:TIMEOUTSALESFORCE:TIMEOUT means a request to Salesforce took longer than the configured amount of time. Reduce the work in the request, or raise the timeout on the connector configuration.
- SALESFORCE:UNAVAILABLESALESFORCE:UNAVAILABLE means the Salesforce server is unavailable. Retry later, and check the org's status before changing the app.
Scatter-Gather router1
SFTP Connector12
- SFTP Connector fails with a PPK identity fileSFTP Connector 2.0.0 and later cannot use a PPK identity file for public key authentication, because the Apache Mina library does not support that format. Convert the key to PEM with PuTTYgen and point the identity file setting at the PEM file.
- SFTP Write in APPEND mode overwrites the file or failsWhen SFTP Write in APPEND mode overwrites the file or fails with a generic error, the server is a legacy one that lacks the SSH_FXF_APPEND flag. Set Write Strategy to CUSTOM and Write Mode to CUSTOM_APPEND.
- SFTP:ACCESS_DENIEDSFTP:ACCESS_DENIED means the operation tried to do something on an SFTP path that the connected user has no permission for. Grant that user the permission on the server, or connect as a user that has it.
- SFTP:CANNOT_REACHSFTP:CANNOT_REACH means an error occurred while connecting to the SFTP server host and port. Typically the remote side refuses the connection, for example because nothing is listening on that address and port.
- SFTP:CONNECTION_TIMEOUTSFTP:CONNECTION_TIMEOUT means the attempt to connect to the SFTP server timed out. Confirm the server is reachable from where the Mule app runs before changing anything in the flow.
- SFTP:CONNECTIVITYSFTP:CONNECTIVITY means the connection to the SFTP server was interrupted. Check the network path and the server, and compare the server's log with the Mule app's log for the same moment.
- SFTP:DISCONNECTEDSFTP:DISCONNECTED means the app made too many failed login attempts to the server. The most common cause is invalid credentials, so fix those first.
- SFTP:FILE_ALREADY_EXISTSSFTP:FILE_ALREADY_EXISTS means the operation tried to create a file where a file with the same name already exists. It happens, for example, when Write uses the CREATE_NEW mode on an existing file's path, so change the write mode or the target name.
- SFTP:ILLEGAL_PATHSFTP:ILLEGAL_PATH means the path given to the SFTP operation is invalid, for example because it does not exist. Correct the path, or create the directory on the server first.
- SFTP:INVALID_CREDENTIALSSFTP:INVALID_CREDENTIALS means authentication against the SFTP server failed because the credentials are invalid. Correct the user, password or key in the SFTP connection configuration.
- SFTP:KEY_EXCHANGE_FAILEDSFTP:KEY_EXCHANGE_FAILED means the app started an SSH connection to the server and failed at the key exchange step. Compare the algorithms the server requires with what the connector offers, using the server configuration and SSH trace logging.
- SFTP:UNKNOWN_HOSTSFTP:UNKNOWN_HOST means Mule cannot determine the IP address of the SFTP host. Fix the host name in the connection configuration, or the DNS resolution where the app runs.
Spike Control policy1
Until Successful scope1
Validation Module15
- VALIDATION:BLANK_STRINGVALIDATION:BLANK_STRING is thrown by the Validation module's Is not blank string operation when the string is blank. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:EMPTY_COLLECTIONVALIDATION:EMPTY_COLLECTION is thrown by the Validation module's Is not empty collection operation when the collection is empty. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:INVALID_BOOLEANVALIDATION:INVALID_BOOLEAN is thrown by the Validation module's Is true and Is false operations when the expression did not evaluate to the expected boolean. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:INVALID_EMAILVALIDATION:INVALID_EMAIL is thrown by the Validation module's Is email operation when the value is not a valid email address. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:INVALID_IPVALIDATION:INVALID_IP is thrown by the Validation module's Is IP, Is allowed IP and Is not denied IP operations when the value is not a valid IP address. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:INVALID_NUMBERVALIDATION:INVALID_NUMBER is thrown by the Validation module's Is number operation when the value is not a valid number for the configured settings. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:INVALID_SIZEVALIDATION:INVALID_SIZE is thrown by the Validation module's Validate size operation when the size of the value is outside the configured range. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:INVALID_TIMEVALIDATION:INVALID_TIME is thrown by the Validation module's Is time operation when the value is not a valid time for the configured pattern. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:INVALID_URLVALIDATION:INVALID_URL is thrown by the Validation module's Is URL operation when the value is not a valid URL. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:MISMATCHVALIDATION:MISMATCH is thrown by the Validation module's Matches regex operation when the value does not match the regular expression. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:MULTIPLEVALIDATION:MULTIPLE is the single error the Validation module's All and Any scopes raise to summarize the validations that failed inside them. Read the error description to see which validations failed, then fix those values.
- VALIDATION:NOT_EMPTY_COLLECTIONVALIDATION:NOT_EMPTY_COLLECTION is thrown by the Validation module's Is empty collection operation when the collection was expected to be empty but has elements. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:NOT_NULLVALIDATION:NOT_NULL is thrown by the Validation module's Is null operation when a value was expected to be null but is not. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:NULLVALIDATION:NULL is thrown by the Validation module's Is not null operation when the value is null. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:REJECTED_IPVALIDATION:REJECTED_IP is thrown by the Validation module's Is allowed IP and Is not denied IP operations when the IP address is not allowed by the configured list. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
VM Connector1
Web Service Consumer Connector8
- Maximum attribute size limit (524288) exceededThis error means a SOAP message has an XML attribute longer than the default limit of 524288 characters. Raise the limit with the system property mule.soap.maxAttributeSize.
- No Content-Type boundled in the messageThis error is thrown by Web Service Consumer Connector 1.10.0 and earlier when the response has no Content-Type. From version 1.10.1 it is not thrown when Content-Type is missing and the status is not 200, so upgrade the connector.
- WSC:BAD_REQUESTWSC:BAD_REQUEST means the operation does not exist in the WSDL, or the request body is not valid XML. Pick an operation the WSDL defines and build the body as well-formed XML.
- WSC:CANNOT_DISPATCHWSC:CANNOT_DISPATCH is raised when the request cannot be dispatched and the HTTP error cannot be turned into a SOAP fault. In version 3.0 that covers one-way operations, WSDL or schema requests, an empty HTTP error body, or an error body over 1048576 bytes.
- WSC:EMPTY_RESPONSEWSC:EMPTY_RESPONSE occurs when mandatory fields are missing from the SOAP response (Illegal Empty Response). Inspect the HTTP status and headers on the error and check what the service actually returned.
- WSC:INVALID_WSDLWSC:INVALID_WSDL means the WSDL is poorly formatted. Validate the WSDL in a viewer and, if it is loaded from a remote host, confirm the app can reach that host.
- WSC:SOAP_FAULTWSC:SOAP_FAULT means the SOAP service returned a fault, or the response did not match the format in the WSDL. Read the fault text in error.errorMessage.payload.reason and the detail in error.errorMessage.payload.detail.
- WSC:SOAP_FAULT with faultcode soap:MustUnderstandA WSC:SOAP_FAULT with the fault code soap:MustUnderstand happens because the connector's security Must Understand field defaults to true and the service does not process that header. Set Must Understand to false.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer
The iPaaS Brief
Subscribe to The iPaaS Brief.
The iPaaS newsletter for the people who run integrations. From iPaaS Group.
Free. You finish on theipaasbrief.com and confirm by email.