[Bug] Skywalking local setup unable to configure for multiple services

[MenusGarg5981]

Search before asking

• I had searched in the issues and found no similar issues.

Apache SkyWalking Component

OAP server (apache/skywalking)

What happened

Hello everyone, I was trying to configure skywalking locally for multiple services(2) using a java agent. In the agent.config, file I mentioned the backend service address to 127.0.0.1:11800 for both the services and OAP running at 12800, both were spring boot applications one pointed at 8080 and the other at 8082 while the skywalking server was pointed at 8081.
Logs showed up that:

Caused by: org.apache.skywalking.apm.dependencies.io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:11800
Caused by: java.net.ConnectException: Connection refused
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at org.apache.skywalking.apm.dependencies.io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:330)
	at org.apache.skywalking.apm.dependencies.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
	at org.apache.skywalking.apm.dependencies.io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:702)
	at org.apache.skywalking.apm.dependencies.io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
	at org.apache.skywalking.apm.dependencies.io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
	at org.apache.skywalking.apm.dependencies.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
	at org.apache.skywalking.apm.dependencies.io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
	at org.apache.skywalking.apm.dependencies.io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at org.apache.skywalking.apm.dependencies.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.lang.Thread.run(Thread.java:748)

How should I configure it for both the services to show up on the same UI?

What you expected to happen

Both the services are trying to send the metrics at the same gRPC port so maybe this is the reason.

How to reproduce

Trying to configure multiple services using this documentation: https://skywalking.apache.org/docs/main/v8.4.0/en/setup/service-agent/java-agent/readme/

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

I am not sure your points. The Connection refused means the connection between agent and OAP server is not established. So, no data sent out.

Is your OAP server really listening to 127.0.0.1:11800? This is a local address and you should check OAP logs to see whether the server starting up successfully.

BTW, this is not a bug report. Please follow the community guidance.

[ZovenCraig]

It's solved.Add below content in agent.config or cmd line parameter.It's new parameter from v8.4.0
plugin.toolkit.log.grpc.reporter.server_host=${SW_GRPC_LOG_SERVER_HOST:your oap ip address}
plugin.toolkit.log.grpc.reporter.server_port=${SW_GRPC_LOG_SERVER_PORT:11800}
plugin.toolkit.log.grpc.reporter.max_message_size=${SW_GRPC_LOG_MAX_MESSAGE_SIZE:10485760}
plugin.toolkit.log.grpc.reporter.upstream_timeout=${SW_GRPC_LOG_GRPC_UPSTREAM_TIMEOUT:30}

[yinyuncan]

谢谢 ，这个问题我找了很久

[yijieshusheng-git]

thanks,how to config multpile addresses?

[Garden12138]

you can also add VM options like this:
-javaagent:${install_path}/apache-skywalking-apm-bin/agent/skywalking-agent.jar -Dskywalking.agent.service_name=${service_name} -Dskywalking.collector.backend_service=${skywalking_aop_address} -Dskywalking.plugin.toolkit.log.grpc.reporter.server_host=${skywalking_aop_ip} -Dskywalking.plugin.toolkit.log.grpc.reporter.server_port=${skywalking_aop_port}

[fengyuwusong]

I am deeply grateful for your help! This issue has been a source of frustration for me for quite some time, but thanks to your assistance, it has finally been resolved.