Error Message Codes
Error Message Codes
The following error message codes may appear on logs or API responses. Use the following message code references and the corresponding reasons and actions to help troubleshoot issues.
API mediation utility messages
ZWEAM000I
%s started in %s seconds
Reason:
The service started.
Action:
No action required.
API mediation common messages
ZWEAO102E
Gateway not yet discovered. The Transform service cannot perform the request
Reason:
The Transform service was requested to transform a url, but the Gateway instance was not discovered.
Action:
Do not begin performing requests until the API Mediation Layer fully initializes after startup. Check that your Discovery service is running and that all services (especially the Gateway) are discovered correctly.
ZWEAO104W
GatewayInstanceInitializer has been stopped due to exception: %s
Reason:
An unexpected exception occurred while retrieving the Gateway service instance from the Discovery Service.
Action:
Check that both the service and the Gateway can register with Discovery. If the services are not registering, investigate the reason why. If no cause can be determined, create an issue.
ZWEAO105W
Gateway HTTP Client per-route connection limit (maxConnectionsPerRoute) of %s has been reached for the '%s' route.
Reason:
Too many concurrent connection requests were made to the same route.
Action:
Further connections will be queued until there is room in the connection pool. You may also increase the per-route connection limit via the gateway start-up script by setting the Gateway configuration for maxConnectionsPerRoute.
ZWEAO106W
Gateway HTTP Client total connection limit (maxTotalConnections) of %s has been reached.
Reason:
Too many concurrent connection requests were made.
Action:
Further connections will be queued until there is room in the connection pool. You may also increase the total connection limit via the gateway start-up script by setting the Gateway configuration for maxTotalConnections.
ZWEAO401E
Unknown error in HTTPS configuration: '%s'
Reason:
An Unknown error occurred while setting up an HTTP client during service initialization, followed by a system exit.
Action:
Start the service again in debug mode to get a more descriptive message. This error indicates it is not a configuration issue.
Common service core messages
ZWEAM100E
Could not read properties from: '%s'
Reason:
The Build Info properties file is empty or null.
Action:
The jar file is not packaged correctly. Please submit an issue.
ZWEAM101E
I/O Error reading properties from: '%s' Details: '%s'
Reason:
I/O error reading META-INF/build-info.properties
or META-INF/git.properties
.
Action:
The jar file is not packaged correctly. Please submit an issue.
ZWEAM102E
Internal error: Invalid message key '%s' is provided. Please create an issue with this message.
Reason:
Message service is requested to create a message with an invalid key.
Action:
Create an issue with this message.
ZWEAM103E
Internal error: Invalid message text format. Please create an issue with this message.
Reason:
Message service is requested to create a message with an invalid text format.
Action:
Create an issue with this message.
ZWEAM104E
The endpoint you are looking for '%s' could not be located
Reason:
The endpoint you are looking for could not be located.
Action:
Verify that the URL of the endpoint you are trying to reach is correct.
ZWEAG140E
The 'applicationName' parameter name is missing.
Reason:
The application name is not provided.
Action:
Provide the 'applicationName' parameter.
ZWEAG141E
The generation of the PassTicket failed. Reason: %s
Reason:
An error occurred in the SAF Auth Service. Review the reason in the error message.
Action:
Supply a valid user and application name, and check that corresponding permissions have been set up.
ZWEAM400E
Error initializing SSL Context: '%s'
Reason:
An error occurred while initializing the SSL Context.
Action:
Refer to the specific message to identify the exact problem. Possible causes include:
- Incorrect security algorithm
- The keystore is invalid or corrupted
- The certificate is invalid or corrupted
ZWEAM500W
The service is not verifying the TLS/SSL certificates of the services
Reason:
This is a warning that the SSL Context will be created without verifying certificates.
Action:
Stop the service and set the verifySslCertificatesOfServices parameter to true
, and then restart the service. Do not use this option in a production environment.
ZWEAM501W
Service is connecting to Discovery service using the non-secure HTTP protocol.
Reason:
The service is connecting to the Discovery Service using the non-secure HTTP protocol.
Action:
For production use, start the Discovery Service in HTTPS mode and configure the services accordingly.
ZWEAM502E
Error reading secret key: '%s'
Reason:
A key with the specified alias cannot be loaded from the keystore.
Action:
Ensure that the configured key is present, in the correct format, and not corrupt.
ZWEAM503E
Error reading secret key: '%s'
Reason:
Error reading secret key.
Action:
Refer to the specific message to identify the exact problem. Possible causes include:
- An incorrect security algorithm
- The keystore is invalid or corrupted
- The certificate is invalid or corrupted
ZWEAM504E
Error reading public key: '%s'
Reason:
Error reading secret key.
Action:
Refer to the specific message to identify the exact problem. Possible causes include:
- An incorrect security algorithm
- The keystore is invalid or corrupted
- The certificate is invalid or corrupted
ZWEAM505E
Error initializing SSL/TLS context: '%s'
Reason:
Error initializing SSL/TLS context.
Action:
Refer to the specific message to identify the exact problem. Possible causes include:
- An incorrect security algorithm
- The keystore is invalid or corrupted
- The certificate is invalid or corrupted
ZWEAM506E
Truststore Password configuration parameter is not defined
Reason:
Your truststore password was not set in the configuration.
Action:
Ensure that the parameter server.ssl.trustStorePassword contains the correct password for your truststore.
ZWEAM507E
Truststore configuration parameter is not defined but it is required
Reason:
The truststore usage is mandatory, but the truststore location is not provided.
Action:
If a truststore is required, define the truststore configuration parameter by editing the server.ssl.truststore, server.ssl.truststorePassword and server.ssl.truststoreType parameters with valid data. If you do not require a truststore, change the trustStoreRequired boolean parameter to false
.
ZWEAM508E
Keystore not found, server.ssl.keyStore configuration parameter is not defined
Reason:
Your keystore path was not set in the configuration.
Action:
Ensure that the correct path to your keystore is contained in the parameter server.ssl.keyStore in the properties or yaml file of your service.
ZWEAM509E
Keystore password not found, server.ssl.keyStorePassword configuration parameter is not defined
Reason:
Your keystore password was not set in the configuration.
Action:
Ensure that the correct password to your keystore in the parameter server.ssl.keyStorePassword is contained in the properties or yaml file of your service.
ZWEAM510E
Invalid key alias '%s'
Reason:
The key alias was not found.
Action:
Ensure that the key alias provided for the key exists in the provided keystore.
ZWEAM511E
There was a TLS request error accessing the URL '%s': '%s'
Reason:
The Gateway refuses to communicate with the requested service.
Action:
Possible actions regarding to message content:
- Message: The certificate is not trusted by the API Gateway. Action: Verify trust of the certificate is the issue by disabling certificate verification and retry the request.
- Message: Certificate does not match any of the subject alternative names. Action: Verify that the hostname which the certificate is issued for matches the hostname of the service.
- Message: Unable to find the valid certification path to the requested target. Action: Import the root CA that issued services' certificate to API Gateway truststore.
- Message: Verify the requested service supports TLS. Action: Ensure the requested service is running with TLS enabled.
- Message: Review the APIML debug log for more information. Action: Enable APIML debug mode and retry the request, then review the APIML log for TLS errors.
ZWEAM600W
Invalid parameter in metadata: '%s'
Reason:
An invalid apiInfo parameter was found while parsing the service metadata.
Action:
Remove or fix the referenced metadata parameter.
ZWEAM700E
No response received within the allowed time: %s
Reason:
No response was received within the allowed time.
Action:
Verify that the URL you are trying to reach is correct and all services are running.