# APM application\_packages for WebLogic **URL:** \ **Category:** APM\ **Tags:** java\ **Created:** [January 29, 2020, 7:40pm UTC](https://discuss.elastic.co/t/apm-application-packages-for-weblogic/217069 "2020-01-29T19:40:41Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Sirius](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sirius/32/47012_2.png) [@Sirius](https://discuss.elastic.co/u/Sirius)\ **Post date:** [January 29, 2020, 7:40pm UTC](https://discuss.elastic.co/t/apm-application-packages-for-weblogic/217069/1 "2020-01-29T19:40:41Z")
I have running APM java agent for weblogic which is streaming fine to APM serve in this case only for usage resource metrics as default. At this point I'm not getting traces / transactions / errors information, is that because I have to set "pplication\_packages" property right ?, if so, my doubt is ... is there way to specify in the property get all java projects ? Since our weblogic is running a large list of type Java projects like libraries, Web App, Enterprise Application, etc., I think it should be inefficient setting whole list. export JAVA\_OPTIONS="$JAVA\_OPTIONS -Delastic.apm.application\_packages=org.example,org.another.example" ---
**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:** [January 30, 2020, 6:27am UTC](https://discuss.elastic.co/t/apm-application-packages-for-weblogic/217069/2 "2020-01-30T06:27:18Z")
Hi and thanks for reaching out. You normally don't need to set `application_packages` in order to get basic traces, as long as you are using [supported technologies/frameworks](https://www.elastic.co/guide/en/apm/agent/java/current/supported-technologies-details.html). Please go over this page and make sure you are using a supported WebLogic version, Java version and libraries. The `application_packages` is required to better name your transactions if you are using JAX-RS and JAX-WS, but as long as there is a Servlet handling all requests, you should have got something traced. In any case, it is best not to set this config **with invalid packages** - either set with correct package names or omit it. Please go over our documentation throughly, including the [troubleshooting](https://www.elastic.co/guide/en/apm/agent/java/current/trouble-shooting.html) page and you should be able to sort this out. In any case, without knowing your setup and getting a debug level log, there is very little we can say. ---
**Author:** ![Sirius](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sirius/32/47012_2.png) [@Sirius](https://discuss.elastic.co/u/Sirius)\ **Post date:** [January 30, 2020, 7:38pm UTC](https://discuss.elastic.co/t/apm-application-packages-for-weblogic/217069/3 "2020-01-30T19:38:03Z")
Hi Eyal Thanks for the feedback. I see below log output, is that the reason of not capturing traces ? One more observation, Weblogic running version is 10.3.x, asper supported technologies document only supports WebLogic 12.2. Upgrating WebLogic and Java could be the solution ? Log : > 2020-01-29 15:49:16.704 [apm-server-healthcheck] INFO co.elastic.apm.agent.report.ApmServerHealthChecker - **Elastic APM server is available:** { "build\_date": "2019-12-16T20:57:59Z", "build\_sha": "348d8d83c3c823b64fc0692be607b1a5a8fac775", "version": "7.5.1"} > 2020-01-29 15:49:16.870 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - Starting Elastic APM 1.12.0 as MyWebLogicApp on Java 1.7.0\_80 (Oracle Corporation) Linux 2.6.32-754.24.3.el6.x86\_64 > 2020-01-29 15:49:16.871 [main] WARN co.elastic.apm.agent.configuration.StartupInfo - To enable all features and to increase startup times, please configure application\_packages > The selected version of Java, 1.7.0\_80, contains a known security flaw. Please upgrade to at least 1.7.0\_131 > 2020-01-29 15:49:35.475 [[ACTIVE] ExecuteThread: '80' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN co.elastic.apm.agent.bci.bytebuddy.ErrorLoggingListener - weblogic.jdbc.sqlserverbase.BaseConnection uses an **unsupported** class file version (pre Java 5) and can't be instrumented. Consider updating to a newer version of that library. > 2020-01-29 15:49:35.584 [[ACTIVE] ExecuteThread: '80' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN co.elastic.apm.agent.bci.bytebuddy.ErrorLoggingListener - weblogic.jdbc.db2base.BaseConnection uses an **unsupported** class file version (pre Java 5) and can't be instrumented. Consider updating to a newer version of that library. > 2020-01-29 15:49:35.742 [[ACTIVE] ExecuteThread: '80' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN co.elastic.apm.agent.bci.bytebuddy.ErrorLoggingListener - weblogic.jdbc.sybasebase.BaseConnection uses an **unsupported** class file version (pre Java 5) and can't be instrumented. Consider updating to a newer version of that library. > 2020-01-29 15:49:35.856 [[ACTIVE] ExecuteThread: '80' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN co.elastic.apm.agent.bci.bytebuddy.ErrorLoggingListener - weblogic.jdbc.informixbase.BaseConnection uses an **unsupported** class file version (pre Java 5) and can't be instrumented. Consider updating to a newer version of that library. This is my configuration: > export JAVA\_OPTIONS="$JAVA\_OPTIONS -javaagent:/mypath/elastic-apm-agent-1.12.0.jar" > export JAVA\_OPTIONS="$JAVA\_OPTIONS -Delastic.apm.service\_name=MyWebLogicApp" > #export JAVA\_OPTIONS="$JAVA\_OPTIONS -Delastic.apm.application\_packages=org.example,org.another.example" > export JAVA\_OPTIONS="$JAVA\_OPTIONS -Delastic.apm.server\_urls=[http://apmserver:8200](http://apmserver:8200)" Regards, Jorge ---
**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:** [February 2, 2020, 6:16am UTC](https://discuss.elastic.co/t/apm-application-packages-for-weblogic/217069/4 "2020-02-02T06:16:31Z")
Yes, this is definitely the case of using unsupported versions of WebLogic and JVM. Upgrading to the supported versions is expected to solve this. ---
**Author:** ![Sirius](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sirius/32/47012_2.png) [@Sirius](https://discuss.elastic.co/u/Sirius)\ **Post date:** [February 4, 2020, 10:34pm UTC](https://discuss.elastic.co/t/apm-application-packages-for-weblogic/217069/5 "2020-02-04T22:34:48Z")
Thanks, I've tested same configuration running with WebLogic 12.2 and worked as expected ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 25, 2020, 6:34pm UTC](https://discuss.elastic.co/t/apm-application-packages-for-weblogic/217069/6 "2020-02-25T18:34:56Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.