# Tanuki java wrapper - standalone java application **URL:** \ **Category:** APM\ **Tags:** java\ **Created:** [June 21, 2019, 1:02pm UTC](https://discuss.elastic.co/t/tanuki-java-wrapper-standalone-java-application/186885 "2019-06-21T13:02:51Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![tmihaldinec](https://avatars.discourse-cdn.com/v4/letter/t/ccd318/32.png) [@tmihaldinec](https://discuss.elastic.co/u/tmihaldinec)\ **Post date:** [June 21, 2019, 1:02pm UTC](https://discuss.elastic.co/t/tanuki-java-wrapper-standalone-java-application/186885/1 "2019-06-21T13:02:51Z")
If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text 🙂 **Kibana version** : 7.1.1 **Elasticsearch version** : 7.1.1 **APM Server version** :7.1.1 **APM Agent language and version** : 1.7.0 **Browser version** : N/A **Original install method (e.g. download page, yum, deb, from source, etc.) and version**: yum RHEL 7.5 **Fresh install or upgraded from other version?** N/A long story short.. we are using Tanuki java wrapper for starting of our Java 1.8 apps if we use Tanuki java wrapper to instrumentalize Wildfly 15 it works OK but if we want to start standalone java application we see that it regeistered itself in APM but there is no transactions i can only see CPU and Memory metrics so, question is.. is there any reason why it doesn't work? it is JDK 1.8.202 config of wrapper is: ######## Wrapper Java Properties ######### wrapper.java.command=java set.JAVA\_HOME=/opt/appp/java/java8/ wrapper.java.command=%JAVA\_HOME%/bin/java wrapper.java.command.loglevel=ERROR ####### Java Evironment ########### set.OPCO=XXX set.JARPATH=/opt/appp/%OPCO%/PE/lib set.CONFIGPATH=/opt/appp/%OPCO%/PE/cfg set.LOGPATH=/var/opt/appp/%OPCO%/log/PE ######## Java Classpath properties ######## wrapper.java.classpath.1=/opt/appp/wrapper/lib/wrapper.jar wrapper.java.classpath.2=app.jar wrapper.java.classpath.3=%JARPATH%/\*.jar wrapper.java.classpath.4=%CONFIGPATH% wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp wrapper.java.library.path.1=/opt/appp/wrapper/lib ######## Additional Properties####### wrapper.java.additional.auto\_bits=TRUE wrapper.java.additional.1=-Xmx768m wrapper.java.additional.2=-D[APPEE] wrapper.java.additional.3=-Daxis.ClientConfigFile=%CONFIGPATH%/client-config.wsdd wrapper.java.additional.30=-javaagent:/opt/appp/deploy/elastic-apm-agent.jar wrapper.java.additional.31=-Delastic.apm.service\_name=MyAPPEE wrapper.java.additional.32=-Delastic.apm.application\_packages=org.apache wrapper.java.additional.33=-Delastic.apm.server\_urls=http://11.11.11.11:8200 wrapper.java.additional.34=-Delastic.apm.capture\_headers=true wrapper.app.parameter.1=com.app.apppcee.pe.PEMain wrapper.app.parameter.2=-start wrapper.app.parameter.3=-config wrapper.app.parameter.4=%CONFIGPATH%/Configuration.xml update1: in logs i can see that apm agent successfully started: wrapper.log:INFO | jvm 1 | 2019/06/21 15:28:46 | 2019-06-21 15:28:46.350 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - Starting Elastic APM 1.7.0 as MkaProvisioningEngine on Java 1.8.0\_212 (Oracle Corporation) Linux 2.6.32-754.2.1.el6.x86\_64 wrapper.log:INFO | jvm 1 | 2019/06/21 15:28:46 | 2019-06-21 15:28:46.369 [apm-server-healthcheck] INFO co.elastic.apm.agent.report.ApmServerHealthChecker - Elastic APM server is available: { "build\_date": "2019-05-23T12:59:32Z", "build\_sha": "410bf33fa1b67fa5bd02a388de17d0e30ec031da", "version": "7.1.1"} wrapper.log:INFO | jvm 1 | 2019/06/21 15:29:17 | 2019-06-21 15:29:17.748 [RequestProcessor-10] WARN co.elastic.apm.agent.bci.bytebuddy.ErrorLoggingListener - org.apache.commons.dbcp.PoolableConnection uses an unsupported class file version (pre Java 5) and can't be instrumented. Consider updating to a newer version of that library. thanks tomislav ---
**Author:** ![Eyal\_Koren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eyal_koren/32/36830_2.png) [@Eyal\_Koren](https://discuss.elastic.co/u/Eyal_Koren)\ **Post date:** [June 23, 2019, 5:29am UTC](https://discuss.elastic.co/t/tanuki-java-wrapper-standalone-java-application/186885/2 "2019-06-23T05:29:39Z")
Hi Tomislav, welcome to the forum 🙂 We automatically trace servlet containers by instrumenting the Servlet API for Transaction creation. Even if we instrument other stuff automatically (like JDBC or HTTP clients), we will not capture them unless they are executed within traced transactions. This is why you get data for WildFly and not for your standalone app, where we have no way of identifying a proper location to start and end transactions. Fortunately, we have a [public API](https://www.elastic.co/guide/en/apm/agent/java/current/public-api.html) you can use in order to manually instrument and trace arbitrary Java apps. Through this API you can start/activate/deactivate/end Transactions, spans, capture errors and much more. Please go over it carefully - if you fully understand how to use it and maintain proper states of Spans and Transactions it can give you a lot of flexibility to get what you want. I hope this helps, Eyal. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 14, 2019, 1:29am UTC](https://discuss.elastic.co/t/tanuki-java-wrapper-standalone-java-application/186885/3 "2019-07-14T01:29:41Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.