Troubleshoot Kaazing Gateway Clusters and Load Balancing
When you configure Kaazing Gateway for high availability, you may encounter one of the following errors. To resolve an issue, follow the guidance provided for the associated error.
Troubleshooting Kaazing Gateway
This topic is part of Troubleshoot Kaazing Gateway that groups troubleshooting topics into the categories shown in the following table:
What Problem Are You Having? | Topic or Reference |
---|---|
Configuration and startup | Troubleshoot Kaazing Gateway Configuration and Startup |
Clusters and load balancing | Troubleshoot Kaazing Gateway Cluster and Load Balancing |
Security | Troubleshoot Kaazing Gateway Security |
Clients | Troubleshoot Your Clients |
What Problem Are You Having?
- Accept URI: [URI] does not match balance URI: [URI] in all but hostname. Unable to launch Gateway
- Balance URI: [URI] does not point to a balancer service’s accept URI in the configuration file, unable to launch the Gateway
- Detected orphaned balancer accept URI: [URI], no balance URIs in the configuration file point to this balancer service. Unable to launch the Gateway
Accept URI: [URI] does not match balance URI: [URI] in all but hostname. Unable to launch Gateway.
Cause: The balance
and accept
element URIs in a service
must use the same port number and path. The hostnames in the URIs may be different.
Solution: Correct the balance
or accept
URIs by using the same port number and path. In the following example, the balance
and accept
URIs have different hostnames but the same port number (8081
) and path (echo
):
<service> <accept>ws://node1.example.com:8081/echo</accept> <balance>ws://balancer.example.com:8081/echo</balance> <type>echo</type> <cross-site-constraint> <allow-origin>http://directory.example.com:8080</allow-origin> </cross-site-constraint> </service>
Balance URI: [URI] does not point to a balancer service’s accept URI in the configuration file, unable to launch the Gateway.
Cause: The balance
URI in a service
must match the accept
URI in a balancer
service in the same Gateway configuration file (GATEWAY_HOME/conf/gateway-config.xml
).
Solution: Ensure that the balance
URI in a service
matches at least one accept
URI in a balancer
service. In the following example, the accept
URI in the balancer
service matches the balance
URI in the Echo service
:
<service> <accept>ws://balancer.example.com:8081/echo</accept> <type>balancer</type> <accept-options> <ws.bind>192.168.2.10:8081</ws.bind> </accept-options> </service> <service> <accept>ws://node1.example.com:8081/echo</accept> <balance>ws://balancer.example.com:8081/echo</balance> <type>echo</type> <cross-site-constraint> <allow-origin>http://directory.example.com:8080</allow-origin> </cross-site-constraint> </service>
Detected orphaned balancer accept URI: [URI], no balance URIs in the configuration file point to this balancer service. Unable to launch the Gateway.
Cause: There is an accept
URI in a balancer
service that does not have a corresponding balance
URI in a service
. Every accept
URI in a balancer
service must have a corresponding balance
URI in a service
.
Solution: Remove the accept
from the balancer
service or add a corresponding balance
URI to a service
.