address is resolved to unix:

[bastel-123]

Specifications

• Client Version: latest
• InfluxDB Version: latest
• Platform: Java 25

I get the following error message while InfluxDBClient.getInstance (config) "java.lang.RuntimeException: java.lang.IllegalArgumentException: Address types of NameResolver 'unix' for 'unix:///192.168.178.100:8181' not supported by transport". At the clientConfig I defined host ('http:///192.168.178.100:8181').

Code sample to reproduce problem

````java`

### Expected behavior

        String influxHost = resolveInfluxProperty ("INFLUX_HOST", "http://192.168.178.100:8181");
        String influxToken = resolveInfluxProperty ("INFLUX_TOKEN", "...token... ");
        String influxDB = resolveInfluxProperty ("INFLUX_DATABASE", "test");
        
        Duration influxWriteTimeout = Duration.ofMillis(5000L);
        Duration influxQueryTimeout = Duration.ofMillis(5000L);
        
        ClientConfig influxConfig = new ClientConfig.Builder()
            .host (influxHost)
            .token (influxToken.toCharArray())
            .database (influxDB)
            .writeTimeout (influxWriteTimeout)
            .queryTimeout (influxQueryTimeout)
            .build();
        
        try {            
	    influxClient = InfluxDBClient.getInstance (influxConfig);
        } catch (Exception ex) {
        	throw new RuntimeException (ex);
        } 

### Actual behavior

exception  ("java.lang.IllegalArgumentException: Address types of NameResolver 'unix' for 'unix:///pm-docker-2:8181' not supported by transport")


### Additional info

_No response_

[bastel-123]

addition:
The project ist build by maven in Eclipse

[bednar]

You have to use only two slashes in address. This is wrong: http:///192.168.178.100:8181'

[bastel-123]

ok, this was a copy/paste fealure. It's only "http://...", pls. have a look to the source code.

[bastel-123]

Why is this closed?

[bednar]

How do you install your InfluxDB?

[bastel-123]

In a Docker container with docker compose, like this

docker-compose.yml

[bednar]

Thanks for the docker-compose file. The port mapping looks OK for TCP access to InfluxDB on 8181.

Before we dig deeper, could you please confirm how you run the Java application?

• directly from Eclipse
• via Maven
• from a packaged JAR, for example java -jar ...
• inside another Docker container

Please include the exact command or run configuration if possible.

The reason I ask is that this error may happen before the client makes any network connection:

Address types of NameResolver 'unix' ... not supported by transport

In gRPC Java, this can be caused by the runtime classpath or by fat/uber JAR packaging where META-INF/services files are not merged correctly, so gRPC selects the Unix socket resolver instead of the DNS resolver.

Could you also print the resolved host immediately before creating the client?

System.out.println("Resolved Influx host = [" + influxHost + "]");

The value should be exactly something like:

http://192.168.178.100:8181

or, if the Java app runs on the same Docker host:

http://localhost:8181

[bastel-123]

Direct in Eclipse (with Maven) the application works correct.

Starting at a terminal (Ubuntu 24.04) "java -jar myPackage.jar" returns the error I mentioned above.

System.out.println("Resolved Influx host = [" + influxHost + "]"); returns http://192.168.178.100:8181

[bednar]

Thanks, that confirms the important part:

• running directly from Eclipse/Maven works
• running the packaged JAR with java -jar myPackage.jar fails
• the resolved host is correct: http://192.168.178.100:8181

So this does not look like an InfluxDB URL or Docker networking problem. It looks like a packaging/classpath issue in the generated JAR.

Please check the generated JAR content:

jar xf myPackage.jar META-INF/services/io.grpc.NameResolverProvider
cat META-INF/services/io.grpc.NameResolverProvider

That file should include at least:

io.grpc.internal.DnsNameResolverProvider

If it contains only a Unix-domain-socket resolver, gRPC will choose unix as the default resolver and fail with the error you see.

If you build a fat/uber JAR with Maven, make sure META-INF/services files are merged. For maven-shade-plugin, this is usually done with:

<transformer implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/>

Could you please share the part of your pom.xml that creates myPackage.jar? Especially the maven-shade-plugin, maven-assembly-plugin, or any other packaging plugin configuration.

[bastel-123]

cat META-INF/services/io.grpc.NameResolverProvider returns io.grpc.netty.UdsNameResolverProvider

After inserting <transformer implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/> it works now!

Thank you for your great support!!!

Would it a good idea to document this on the main page of this client, since I've already found several references on the web where users were looking for help with the same problem?

[bednar]

Thanks again for confirming the fix. I opened a documentation PR to add a short note about this packaging issue to the README: #406