# Logging the exception thrown during a client/server talk

This scenario applies only to Talend ESB, Talend Data Services Platform, Talend Real-Time Big Data Platform, and Talend Data Fabric.

In this scenario, a Jetty server is started before a client browser requests access to it. Then an exception is thrown at the server side and logged by cErrorHandler.

### In this section

* [Dropping and linking the components](https://help.qlik.com/talend/en-US/mediation-components/8.0/mediation-logs-and-errors/cerrorhandler-cprocessor-cmessagingendpoint-cmessagingendpoint-dropping-and-linking-components)
* [Configuring the components](https://help.qlik.com/talend/en-US/mediation-components/8.0/mediation-logs-and-errors/cerrorhandler-cprocessor-cmessagingendpoint-cmessagingendpoint-configuring-components)
* [Viewing code and executing the Route](https://help.qlik.com/talend/en-US/mediation-components/8.0/mediation-logs-and-errors/cerrorhandler-cprocessor-cmessagingendpoint-cmessagingendpoint-viewing-code-and-executing-route)

**Related reference**

* [cErrorHandler](https://help.qlik.com/talend/en-US/mediation-components/8.0/mediation-logs-and-errors/cerrorhandler "Processes errors in the message routing.")

**Related information**

* [cProcessor](https://help.qlik.com/talend/en-US/mediation-components/8.0/mediation-custom-code/cprocessor)
* [cMessagingEndpoint](https://help.qlik.com/talend/en-US/mediation-components/8.0/mediation-messaging-endpoint/cmessagingendpoint)