This documentation is for older WSO2 products. View documentation for the latest release.
Page Comparison - Troubleshooting Clustering (v.3 vs v.4) - Clustering Guide 4.2.0 - WSO2 Documentation

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

The following are the solutions and possible workarounds that you can use for errors that you encounter.


Tip: Click on the table and use the left and right arrow keys to scroll horizontally.


org.wso2.carbon.server.admin.module.handler.AuthenticationHandler - Illegal access attempt while trying to authenticate APIKeyValidationService {org.wso2.carbon.server.admin.module.handler.AuthenticationHandler}

Check the following:

  • Did you change the default admin password? If so, you need to change the credentials stored in the <APIKeyManager> element of the <APIM_HOME>/repository/conf/api-manager.xml file of the API Gateway node(s).
  • Have you set the priority of the SAML2SSOAuthenticator handler higher than that of the BasicAuthenticator handler? If so, due to an issue in the SAML2SSOAuthenticator handler, it tries to manage the basic authentication requests that come to the publisher/store acs.jag as well.

As a workaround, set a lower priority to the SAML2SSOAuthenticator than the BasicAuthenticator handler in the authenticators.xml file as follows:

Code Block
<Authenticator name="SAML2SSOAuthenticator" disabled="false">
		<Parameter name="LoginPage">/carbon/admin/login.jsp</Parameter>
		<Parameter name="ServiceProviderID">carbonServer</Parameter>
		<Parameter name="IdentityProviderSSOServiceURL">https://localhost:9444/samlsso</Parameter>
		<Parameter name="NameIDPolicyFormat">urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</Parameter>
		<Parameter name="ISAuthnReqSigned">false</Parameter>
 <!-<Parameter name="AssetionConsumerServiceURL">https://localhost:9443/acs</Parameter>->
Error code: 1709It is possible that you may encounter an error (error code: 1709) when starting your cluster using a MySQL database on Microsoft Windows. This error occurs in certain versions of MySQL (5.6.x) and is related to the UTF-8 encoding. MySQL originally used the latin1 character set by default, which stored characters in a 2-byte sequence. In recent versions MySQL defaults to UTF-8 to be friendlier to international users. Use latin1 instead to avoid this problem but note that this may result in issues with non-latin characters (like Hebrew, Japanese, etc.).