valkey-glide: RuntimeException: Current platform supports no known thread pool resources on Amazon Linux 2023

Describe the bug

When attempting to connect to a Redis cluster using the Valkey Glide client in a Spring Boot 3 application on Amazon Linux 2023 (x86_64), I encounter the following error:

java.lang.RuntimeException: Current platform supports no known thread pool resources

java.lang.RuntimeException: Current platform supports no known thread pool resources
        at glide.connectors.resources.Platform.getThreadPoolResourceSupplier(Platform.java:67) ~[valkey-glide-1.1.0-linux-x86_64.jar!/:na]
         at glide.api.BaseClient.createClient(BaseClient.java:363) ~[valkey-glide-1.1.0-linux-x86_64.jar!/:na]
        at glide.api.GlideClient.createClient(GlideClient.java:90) ~[valkey-glide-1.1.0-linux-x86_64.jar!/:na]

This issue does not occur when running the same application on Ubuntu/Debian systems.

The following are system details

Amzona Linux 3:

NAME="Amazon Linux"
VERSION="2023"
ID="amzn"
ID_LIKE="fedora"
VERSION_ID="2023"
PLATFORM_ID="platform:al2023"
PRETTY_NAME="Amazon Linux 2023.6.20241010"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2023"
HOME_URL="https://aws.amazon.com/linux/amazon-linux-2023/"
DOCUMENTATION_URL="https://docs.aws.amazon.com/linux/"
SUPPORT_URL="https://aws.amazon.com/premiumsupport/"
BUG_REPORT_URL="https://github.com/amazonlinux/amazon-linux-2023"
VENDOR_NAME="AWS"
VENDOR_URL="https://aws.amazon.com/"
SUPPORT_END="2028-03-15"

Java version:

openjdk version "17.0.13" 2024-10-15
OpenJDK Runtime Environment Temurin-17.0.13+11 (build 17.0.13+11)
OpenJDK 64-Bit Server VM Temurin-17.0.13+11 (build 17.0.13+11, mixed mode, sharing)

Expected Behavior

The application should successfully connect to the Redis cluster using the Glide client without any runtime exceptions.

Current Behavior

The application fails to establish a connection to the Redis cluster and throws a RuntimeException indicating that no known thread pool resources are available for the current platform.

Reproduction Steps

  1. Set up a Spring Boot 3 application Java 17 with the Valkey Glide client.

Creating the bean as follows in spring boot 3

    @Bean
    @Lazy
    public GlideClient glideClient(ErebusJavaTestingServiceProperties properties, @Value("${redis.cluster.useSsl}") boolean useSsl) throws ExecutionException, InterruptedException {
        String host = properties.getRedisClusterNode();
        int port = properties.getRedisClusterPort();
        LOG.info("Glide Connection to Redis cluster {} at port {} using TLS {}", host, port, useSsl);
        var clientConfiguration = GlideClientConfiguration
                .builder()
                .address(NodeAddress.builder().host(host).port(port).build())
                .useTLS(useSsl)
                .build();
        return GlideClient.createClient(clientConfiguration).get();
    }
  1. Use the Glide client to attempt a connection to a Redis cluster on an Amazon Linux 2023 (x86_64) system.

  2. Observe the error message in the logs.

Possible Solution

No response

Additional Information/Context

The exact application works perfectly fine on debian/ubuntu machine

Client version used

valkey-glide-1.1.0-linux-x86_64.jar

Engine type and version

AWS::ElastiCache::ReplicationGroup 7.1.0

OS

Amazon Linux 2023 - X86_64

Language

Java

Language Version

OpenJDK Runtime Environment Temurin-17.0.13+11

Cluster information

No response

Logs

No response

Other information

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 15 (5 by maintainers)

Most upvoted comments

Dear Glide Team,

I wanted to take a moment to sincerely thank you all for your amazing support in resolving the issue. From the very beginning, I was impressed by your responsiveness and willingness to help. Despite the complexity of the problem, you were patient, diligent, and continuously provided useful suggestions and insights — truly going above and beyond.

After working through all the potential causes, we discovered that the issue was actually related to a server-side configuration. Due to some specific requirements, all our volumes were set to noexec mode, which prevented the Glide client from loading the necessary .so files. Once we identified and corrected this setting, the issue was resolved, and everything is working as expected now.

I deeply appreciate the time and effort you all put into this issue.

Once again, thank you for your continued support