Jacoco Agent running with Dockerd/Tomcat: Error opening zip file or JAR manifest missing

1,602 views
Skip to first unread message

Michael Furmaniuk

unread,
Jan 19, 2017, 11:42:24 AM1/19/17
to JaCoCo and EclEmma Users
I have downloaded the 0.7.8 build from the Jacoco page: http://www.jacoco.org/jacoco/

In trying to set up my local Tomcat build, I would like to run the Jacoco Agent to get my test reports, I place the following configuration:

"JAVA_OPTS=-javaagent:/data/shared/jacoco/lib/jacocoagent.jar=includes=*,output=file,destfile=/data/shared/tests/jacoco/jacoco.exec"


When starting Tomcat I get the following in the Tomcat Log:


Jan 19 16:28:14 sandbox dockerd[1450]: Error opening zip file or JAR manifest missing : /data/shared/jacoco/lib/jacocoagent.jar

Jan 19 16:28:14 sandbox dockerd[1450]: Error occurred during initialization of VM

Jan 19 16:28:14 sandbox dockerd[1450]: agent library failed to init: instrument


Is there some other configuration I need to put in place?  Libraries are in the right location, I downloaded the Jacoco.0.7.8.zip archive and placed the files in the location noted.  Checking their JAR files I do see a Manifest file.  The Tomcat does run in a docker container, if that would make a difference.


java version "1.8.0_102"

Java(TM) SE Runtime Environment (build 1.8.0_102-b14)

Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)


I am running this on OSX Yosemite

Evgeny Mandrikov

unread,
Jan 21, 2017, 9:22:44 AM1/21/17
to JaCoCo and EclEmma Users
Hi,


On Thursday, January 19, 2017 at 5:42:24 PM UTC+1, Michael Furmaniuk wrote:

Jan 19 16:28:14 sandbox dockerd[1450]: Error opening zip file or JAR manifest missing : /data/shared/jacoco/lib/jacocoagent.jar

Jan 19 16:28:14 sandbox dockerd[1450]: Error occurred during initialization of VM

Jan 19 16:28:14 sandbox dockerd[1450]: agent library failed to init: instrument


Please check that file "/data/shared/jacoco/lib/jacocoagent.jar" exists inside of Docker container.
 

 The Tomcat does run in a docker container, if that would make a difference.


Please verify by yourself, whether problem caused by Docker or not - by doing without Docker.

Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages