Does anyone understand why the JVM system property tc.node-name is being used in the codebase? I originally used it in the Session Configurator startup scripts as a way to tag a JVM as taking part in a Configurator session. But somehow it got used as a way to change the JMX object name for the L1Info bean, replacing the DSO Channel's remote address.
Without setting tc.node-name the L1Info bean's name contains: Node=client.host/2361 But with it set to "Tomcat-9081" it becomes Node=Tomcat-9081 This is problematic as the L1Info bean is tunneled into the server and we need a consistent way to discover it. Tc.node-name is screwing that up. I can't find anywhere in the code where this property is actually used.
_______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
