[jgroups-users] Reg - Probe Behaviour on migrating from JGroups 2.11 to Jgroups 3.6.7

Hi,

We are currently moving to Jgroups 3.6.7 from Version Jgroups version 2.11

Tomcat Version : 8.0.18
We are using the tcp config file shipped with the version 3.6.7

In HA cluste,  with version 2.11 we were able to set the level dynamically
for logs by executing

java -cp
/export/home/ecms/tomcat/webapps/admx_ecms/WEB-INF/lib/jgroups-all.jar
org.jgroups.tests.Probe op=UDP.setLevel["trace"]

But when we try to use the command (mentioned below) with updated Jgroups
3.6.7 library, we were not able to see the trace levels getting changed.

java -cp
/export/home/ecms/tomcat/webapps/admx_ecms/WEB-INF/lib/jgroups-3.6.7.Final.jar
org.jgroups.tests.Probe op=UDP.setLevel["trace"]

In my local I have added log4j JAR has to classpath. But with this I can
see the trace only for UDP protocol (local setting uses UDP) in Console.

I have also tried adding -Djgroups.use.jdk_logger=true as per the manual.
That didnot helped much.

Kindly let us know if I am missing anything to change the log level
dynamically.
:-)

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140

_______________________________________________
javagroups-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/javagroups-users