Thanks a lot Evgeny. Yes, I got it now that cli dump is only for agent running in 'tcpserver' output mode.
In our case, we are using output=tcpclient, And as per post link you provided, we have to call RemoteControlWriter.visitDumpCommand(true, false). Do we need to place this call in ExecutionDataServer.java class? or Do I need to execute this from micro service container? On Tuesday, 2 April 2019 23:05:45 UTC+5:30, Evgeny Mandrikov wrote: > > > > On Tuesday, April 2, 2019 at 6:29:24 PM UTC+2, Vijay Nanekar wrote: >> >> >> We have started our micro service with jacoco java agent with tcpclient >> output mode, >> -javaagent:$PWD/coverage/jacocoagent.jar=output=tcpclient,includes=*,address=100.XXX.XXX.XXX,port=6300 >> >> ... >> >> After that, We connect to micro-service machine to dump coverage data on >> the fly (Without shutdown). To do that we execute below jacoco command on >> micro service machine. java -jar coverage/jacococli.jar dump --address >> 100.XXX.XXX.XXX –destfile jacoco-server.exec >> > "dump" from command line interface is not applicable here - quoting its > description ( https://www.jacoco.org/jacoco/trunk/doc/cli.html ): > > Request execution data from a JaCoCo agent running in 'tcpserver' output >> mode. > > > In case of output=tcpclient ExecutionDataServer can request dump from its > client - see > https://groups.google.com/d/msg/jacoco/V7Bmz5r0P24/PdCC5apIoqgJ > > -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/dbebaee3-a268-4be0-8058-5d2a69b663af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
