What Do I Do If Service Registration Fails After Enabling IPv6 for an Exclusive Microservice Engine?

Symptom

A microservice developed based on Java chassis was registered with an exclusive microservice engine with security authentication enabled. The microservice registry center address was the IPv4 address of the engine registry center. The microservice was successfully registered and started.

However, changing the registry center address to the IPv6 address of the engine registry center caused the registration to fail and returned the error "java.net.SocketException: Protocol family unavailable".

Possible Cause

Selecting a VPC network with IPv6 enabled when creating an exclusive microservice engine gives the engine IPv6 support. The IPv6 dual-stack function must be enabled for the selected CCE cluster to deploy services using containers through an IPv6 network segment.

Thus, IPv6 must be enabled for the selected cluster to avoid network disconnection and error.

Solution

1. Modify the microservice application's environment by adding a CCE cluster with the IPv6 dual-stack function enabled.

   For details, see Editing an Environment.

2. Redeploy the application. For details, see Creating and Deploying a Component.