WSO2 Enterprise-Integrator-6-Developer Exam With Confidence Using Practice Dumps

Connection between the ESB and thebackend times out. Socket timeout of the HTTP sender has been ^. exceeded. Solution: Increase the socket timeout of the passthrough HTTP transport. To do that, add the following line to the passthru-http.properties file: http.socket.timeout=120000. Here socket timeout is set to 120000

Connection between the client and the ESB times out. Socket timeout of the HTTP listener has been ^. exceeded. Solution: Increase the socket timeout of the passthrough HTTP transport. To do that, add the following line to the nhttp.properties file: http.socket.timeout= 120000. Here socket timeout is set to 120000.

Connection between the client and the ESB times out. Socket timeout of the HTTP listener has be exceeded. O Solution: Increase the socket timeout of the passthrough HTTP transport. To do that, add the following line to the passthru-http.properties file: http.socket.timeout=120000. Here socket timeout is set to 120000.

Options a,b, and c are incorrect.

Use of class variables is not recommended.

You can define and use a global variable in the mediator class if and only if those variables are shared with all the messages in that particular message flow.

When we use the mediatorin different artifacts, an instance of the mediator gets created for each occurrence in the configuration.

A mediator instance gets created for each occurrence in the configuration and for each message.

Both statement b and c are correct.

It is not possible to set parameters for custom mediators.

Custom mediator's parameters should be declared as public fields in mediator code. For instance: public String foo, bar;

Synapse properties can be used to pass values to mediator arguments. For instance: