mchr3k/org.intrace — Issue #20: Feature request: fixed, non-random trace port for firewall rule
Author: eostermueller
Created: 2012-01-13 13:11:49+00:00
State: open

https://github.com/mchr3k/org.intrace/issues/18#issuecomment-3430561

At the above link, mchr3k gives a good description of the two TCP connections in InTrace.
The 2nd port, the "trace" port, is opened on a random port on the "agent."

In one of our environments, we need to add a firewall rule so the InTrace client can access the trace port.
But we can't do it because a different port is randomly selected on each restart of the agent's JVM.

--Erik