Troubleshooting

Regularly check log files¶

The sedex Client checks important prerequisites for proper operation at startup and during operation. If it detects an error during startup, it terminates itself and writes an error report into the corresponding log file. It is strongly recommended to check the log files regularly and especially after configuration changes.

The error messages in the log files already contain concrete information on how to solve the problem.

Example of an error message in logs\controller\controller-technical.log:

****************************
SEDEX CLIENT FAILED TO START
****************************
Description:
Invalid property in sedex configuration:
    Property: outgoing-web-proxy.host
    Value: http://proxy.example.com
    Reason: Enter only hostname, do not use http:// or https://
Action:
Update your sedex client configuration in <sedex.home>/conf/sedex-
client-configuration.properties

Error codes in the Web Service Proxy access Log¶

Each individual request that is processed by the sedex Web service proxy is recorded in the log file named wsproxy-access-log.csv. A log line in this file contains a lot of information about the initial request by the business application and the response of the target Web service. If problems occur with a particular Web service, this log file is the first place to go.

In particular, the field wsproxy-result is of great relevance and in many cases allows conclusions to be drawn about the causal problem. The following table lists typical error codes and their meanings.

Field wsproxy-result in file wsproxy-access-log.csv	Error	Possible fixes
400 BAD_REQUEST/ INSECURE_BASIC_AUTH	It’s not allowed to use basic authentication over unsecured channels.	Either disable basic authentication or use a secured channel e.g. HTTPS.
400 BAD_REQUEST/ INSECURE_CALL	It’s not allowed to use unsecured HTTP with this Web service.	Access this Web service using HTTPS.
400 BAD_REQUEST/ INVALID_BODY_MISSING_ROUTING_CRITERIA	Content based routing error: The routing element could not be found in the request.	Make sure your Web service request contains a valid value for the defined routing criteria.
401 UNAUTHORIZED/ INVALID_CREDENTIALS	Username and/or password are not correct.	Use the correct credentials for this Web service (username, password).
401 UNAUTHORIZED/ NOT_AUTHENTICATED	This Web service requires an authenticated user.	Add a username and password to the wsproxy-users-configuration file and make sure these are used for basic auth by the business application.
403 FORBIDDEN/ NOT_AUTHORIZED	The user is not authorized to use this Web service.	The associated sedex ID of this user (see wsproxy-users-configuration file) has to be authorized by sedex. Contact your sedex domain administrator or sedex Support.
404 NOT_FOUND/ NO_SUCH_WEBSERVICE_PROVISIONED	The Web service proxy does not offer a Web service at this address.	Verify the address configured in the business application. Check the monitoring page of the sedex Client for available services. If the service is missing, contact your sedex domain administrator or sedex Support.
404 NOT_FOUND/ ENDPOINT_NOT_AVAILABLE	The Web service definition provided by sedex seems to be wrong.	Contact sedex Support.
404 NOT_FOUND/ ENDPOINT_NOT_AVAILABLE_FOR_ROUTING_CRITERIA	Content based routing error: There seems to be no target Web service for the provided routing value.	Make sure your Web service request contains a valid value for the defined routing criteria. Contact sedex Support.
500 INTERNAL_SERVER_ERROR/ NO_WEBSERVICE_DEFINITIONS_AVAILABLE	The Web service definitions could not be provisioned by the sedex server.	Check the log files of your sedex Client for connection problems. Check your internet access. Contact sedex Support.
502 BAD_GATEWAY	The Web service proxy could not connect to the target Web service.	See `wsproxy-technical.log` for details. Check the service response for further hints.