michaeljmarshall commented on issue #13923: URL: https://github.com/apache/pulsar/issues/13923#issuecomment-1404275715
Additional observations: We see this log line once: > 2023-01-16T06:50:07,428 - INFO - [pulsar-client-io-101-2:ClientCnx@269] - [id: 0x053a2e53, L:/127.0.0.1:52810 - R:localhost/127.0.0.1:32794] Connected through proxy to target broker at localhost:6650 We see this one 39 times (where the broker's number changes): > 2023-01-16T06:43:38,845 - INFO - [pulsar-client-io-5-2:ClientCnx@269] - [id: 0x30c84405, L:/127.0.0.1:44442 - R:localhost/127.0.0.1:32784] Connected through proxy to target broker at pulsar-broker-1:6650 The connection to the proxy that fails is associated with this log line: > 2023-01-16T06:43:38,686+0000 [pulsar-proxy-io-2-1] INFO org.apache.pulsar.proxy.server.ProxyConnection - [/172.18.0.1:36040] New connection opened Intriguingly, port 36040 is never referenced as having connected to the broker. I don't see it yet, but this seems like a Java client bug. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
