Support using DIGEST-MD5 as the SASL mechanism for ElasticJob CoordinatorRegistryCenter under GraalVM Native Image

[linghengqian]

Fixes #2099.

Changes proposed in this pull request:

• Support using DIGEST-MD5 as the SASL mechanism for ElasticJob CoordinatorRegistryCenter under GraalVM Native Image.
• For org.apache.curator.test.TestingServer, a lot of system properties are set in the background, refer to https://github.com/apache/zookeeper/blob/release-3.9.2/zookeeper-server/src/test/java/org/apache/zookeeper/test/SaslDigestAuthOverSSLTest.java .
  Therefore, in order to test Zookeeper Server with SASL mechanism enabled under ElasticJob CoordinatorRegistryCenter, ElasticJob should never start Zookeeper Server through org.apache.curator.test.TestingServer. Running Zookeeper Server and Curator Client in the same JVM process will pollute system properties. For more information on this unit test, refer to https://zookeeper.apache.org/doc/r3.9.2/zookeeperAdmin.html and
  https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+and+SASL .
• TODO: The PR is in Not Ready state. It is strange that the saslToken of Zookeeper Quorum member is empty.

10:53:09.890 [main-SendThread(localhost:32791)] INFO org.apache.zookeeper.Login -- Client successfully logged in.
10:53:09.890 [main-SendThread(localhost:32791)] INFO org.apache.zookeeper.client.ZooKeeperSaslClient -- Client will use DIGEST-MD5 as SASL mechanism.
10:53:09.890 [main-SendThread(localhost:32791)] INFO org.apache.zookeeper.ClientCnxn -- Opening socket connection to server localhost/127.0.0.1:32791.
10:53:09.890 [main-SendThread(localhost:32791)] INFO org.apache.zookeeper.ClientCnxn -- SASL config status: Will attempt to SASL-authenticate using Login Context section 'Client'
10:53:09.891 [main-SendThread(localhost:32791)] INFO org.apache.zookeeper.ClientCnxn -- Socket connection established, initiating session, client: /127.0.0.1:46578, server: localhost/127.0.0.1:32791
10:53:09.907 [main-SendThread(localhost:32791)] INFO org.apache.zookeeper.ClientCnxn -- Session establishment complete on server localhost/127.0.0.1:32791, session id = 0x100005a9c630000, negotiated timeout = 40000
10:53:09.907 [main-EventThread] INFO org.apache.curator.framework.state.ConnectionStateManager -- State change: CONNECTED
10:53:09.908 [main] INFO com.zaxxer.hikari.HikariDataSource -- HikariPool-1 - Starting...
10:53:09.910 [main] INFO com.zaxxer.hikari.HikariDataSource -- HikariPool-1 - Start completed.
10:53:09.911 [main] INFO org.apache.shardingsphere.elasticjob.spring.core.setup.SpringProxyJobClassNameProvider -- create SpringProxyJobClassNameProvider
10:53:09.911 [main-SendThread(localhost:32791)] ERROR org.apache.zookeeper.client.ZooKeeperSaslClient -- SASL authentication failed using login context 'Client'.
javax.security.sasl.SaslException: Error in authenticating with a Zookeeper Quorum member: the quorum member's saslToken is null.
        at org.apache.zookeeper.client.ZooKeeperSaslClient.createSaslToken(ZooKeeperSaslClient.java:310)
        at org.apache.zookeeper.client.ZooKeeperSaslClient.respondToServer(ZooKeeperSaslClient.java:270)
        at org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:921)
        at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:98)
        at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:350)
        at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1274)
        at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:853)
        at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:829)
10:53:09.911 [main-EventThread] ERROR org.apache.curator.ConnectionState -- Authentication failed

[linghengqian]

• I used the buildArg of -H:+UnlockExperimentalVMOptions -g -O0 -H:+SourceLevelDebug -H:-DeleteLocalSymbols to attach debug information to the GraalVM Native Image generated by nativeTest, but it seems to be useless. First of all, affected by https://youtrack.jetbrains.com/issue/IDEA-330170 , IntelliJ IDEA's prompts are not intuitive. Affected by Copy APT generated sources into the debugger cache graalvm/native-build-tools#145 , target/source does not carry the local Java code.

sudo apt-get install build-essential zlib1g-dev -y
sdk install java 22.0.2-graalce

cd ./shardingsphere-elasticjob/
sdk use java 22.0.2-graalce
./mvnw -PnativeTestInElasticJob -T1C -e clean test
cp -rf ./test/native/src/test/java/* ./test/native/target/sources/

./test/native/target/native-tests --xml-output-dir ./test/native/target/native-test-reports -Djunit.platform.listeners.uid.tracking.output.dir=./test/native/target/test-ids

• Interestingly, I can run native-tests locally in IntelliJ IDEA, but if I expect to debug native-tests locally in IntelliJ IDEA, IntelliJ IDEA protests. There is no straightforward description in https://www.jetbrains.com/help/idea/debug-graalvm-native.html, it's all dry text, as if assuming that what you see is what you get for the UI.
• 
• 
• https://github.com/nativejdb/nativejdb looks like it's no longer updated and looks like it's about to enter an epic debugging hell. Of course nativejdb does not support jdk22 at all.

[linghengqian]

• gdb local debugging is not available for IntelliJ IDEA, but gdb remote debugging is available for IntelliJ IDEA. IntelliJ IDEA is connected to the Native Image, but it seems that it is not possible to see the internals of variables. All we see is cluttered C++ pointers.

cd ./shardingsphere-elasticjob/
sdk use java 22.0.2-graalce
./mvnw -PnativeTestInElasticJob -T1C -e clean test
gdbserver :1234 ./test/native/target/native-tests --xml-output-dir ./test/native/target/native-test-reports -Djunit.platform.listeners.uid.tracking.output.dir=./test/native/target/test-ids

• 
• 
• 

[linghengqian]

• Waiting for Unable to use GDB to debug the actual value of variables in GraalVM Native Image oracle/graal#9514 .