Loading

How to get more details on Mule Agent WebSocket connectivity errors

Fecha de publicación: Mar 2, 2024
Pasos
GOAL
Get more details on Mule Agent WebSocket connectivity errors. 
com.mulesoft.agent.transport.AbstractWebSocketTransport: Closing Mule Agent WebSocket - Close Code: 1000 - Close Reason: null
com.mulesoft.agent.transport.AbstractWebSocketTransport: Mule Agent WebSocket closed

These lines in the mule-agent.log indicate there is an issue with the WebSocket connection channel. Since this channel is SSL encrypted we are not able to see the error description and error code 1000 is returned, which is too generic to determine the cause of the issue.

PROCEDURE 

* NOTE this procedure is only useful for on-premises instances this error will never be present in CloudHub.

Enable the SSL debug

Set -M-Djavax.net.debug=ssl:handshake parameter on the Java start command.

Or adding the following parameter to the wrapper.conf 
wrapper.java.additional.<n>=-Djavax.net.debug=ssl:handshake
where the n parameter is a integer and is numerically increasing order of the parameters in the conf file.

Or to get more information follow the steps indicated in How to enable SSL debug logging in MuleSoft Products

Then into the mule_ee.log file you will see the SSL debug info, you may need to look for the error between a lot of debug information looking for exceptions or errors related to the hosts of Runtime Manager mentioned here.


 
Número del artículo de conocimiento

001114894

 
Cargando
Salesforce Help | Article