"Active Request" throws an error.

[king1975]

Dear All

All information on the Pinpoint web screen is displayed in my local browser. However, when "REAL TIME" is set, Active Request displays ERROR / NOT FOUND. I think it's a firewall issue. Is there a separate port for "Active Request" information? My Pinpoint Web Version : 2.4.0, 2.5.1 There was no problem when using version 1.8.4.

Agent Config profiler.tcpdatasender.command.accept.enable=true profiler.tcpdatasender.command.activethread.enable=true profiler.tcpdatasender.command.activethread.count.enable=true profiler.tcpdatasender.command.activethread.threaddump.enable=true profiler.tcpdatasender.command.activethread.threadlightdump.enable=true profiler.tcpdatasender.client.write.timeout=3000 profiler.tcpdatasender.client.request.timeout=3000 profiler.tcpdatasender.client.reconnect.interval=3000 profiler.tcpdatasender.client.ping.interval=300000 profiler.tcpdatasender.client.handshake.interval=60000 profiler.tcpdatasender.client.write.buffer.highwatermark=32m profiler.tcpdatasender.client.write.buffer.lowwatermark=16m

Thank you.

[smilu97]

Check if the zookeeper node /pinpoint-cluster/web/${cluster.web.tcp.hostaddress}:${cluster.web.tcp.port} exists, and collector can access with the cluster.web.tcp.hostaddress.

cluster.web.tcp.hostaddress is a property which normally does not require to be manually setup, but automatically be decided by choosing the first of available net interfaces. This sometimes chooses inappropriate net which collector cannot access, and you need to manually set this property