# Incompatibility while using co.elastic.apm:apm-opentracing:1.6.1 and elastic-apm-agent-1.6.1 **URL:** \ **Category:** APM\ **Tags:** java\ **Created:** [May 24, 2019, 11:17am UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628 "2019-05-24T11:17:57Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Barry\_Zhong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/barry_zhong/32/46786_2.png) [@Barry\_Zhong](https://discuss.elastic.co/u/Barry_Zhong)\ **Post date:** [May 24, 2019, 11:17am UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628/1 "2019-05-24T11:17:58Z")
**Kibana version** : 6.5.4 **Elasticsearch version** : 6.5.4 **APM Server version** : 6.5.4 **APM Agent language and version** : Java elastic-apm-agent-1.6.1 **Browser version** : Chrome Version 74.0.3729.169 (Official Build) (64-bit) **Original install method (e.g. download page, yum, deb, from source, etc.) and version**: download page **Fresh install or upgraded from other version?** Fresh install **Is there anything special in your setup?** to enable Reactive Spring (reactor) APM, I am using the following combination: ```auto io.opentracing.contrib opentracing-spring-cloud-starter 0.2.6 co.elastic.apm apm-opentracing 1.6.1 ``` **Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**: ![46%20PM](https://us1.discourse-cdn.com/elastic/original/3X/7/9/792d6e3ad73d01163cb2e8b4d8a0e4d3ddcd4aa0.png) **Steps to reproduce** : I thought it would be an obvious reason, so forgive me to skip this part. **Errors in browser console (if relevant)**: n/a **Provide logs and/or server output (if relevant)**: ```auto gateway_1 | 2019-05-24 10:58:26.651 [apm-reporter] WARN co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - {"accepted":14,"errors":[{"message":"Problem validating JSON document against schema: I[#] S[#] doesn't validate with \"span#\"\n I[#] S[#/allOf/0] allOf failed\n I[#/context/tags/http_status_code] S[#/allOf/0/properties/context/properties/tags/patternProperties/%5E%5B%5E.%2A%22%5D%2A$/type] expected string or null, but got number","document":"{\"span\":{\"name\":\"GET\",\"timestamp\":1558695496561368,\"id\":\"9728c7a0a10689a0\",\"trace_id\":\"449b74106bba1b596a9072da1da6d00d\",\"transaction_id\":\"cb71b6fbd0152a53\",\"parent_id\":\"cb71b6fbd0152a53\",\"duration\":37.993,\"stacktrace\":[{\"filename\":\"TracingClientResponseSubscriber.java\",\"function\":\"onComplete\",\"library_frame\":true,\"lineno\":105,\"abs_path\":\"io.opentracing.contrib.spring.web.client.TracingClientResponseSubscriber\"}, ``` ---
**Author:** ![felixbarny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felixbarny/32/27341_2.png) [@felixbarny](https://discuss.elastic.co/u/felixbarny)\ **Post date:** [May 24, 2019, 11:23am UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628/2 "2019-05-24T11:23:10Z")
Hi and thanks for your question. In order to leverage number and boolean tags (which `opentracing-spring-cloud-starter` apparently makes use of), you have to upgrade to APM Server 6.7. ---
**Author:** ![Barry\_Zhong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/barry_zhong/32/46786_2.png) [@Barry\_Zhong](https://discuss.elastic.co/u/Barry_Zhong)\ **Post date:** [May 24, 2019, 11:24am UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628/3 "2019-05-24T11:24:12Z")
is there a migration guide? ---
**Author:** ![felixbarny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felixbarny/32/27341_2.png) [@felixbarny](https://discuss.elastic.co/u/felixbarny)\ **Post date:** [May 24, 2019, 11:31am UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628/4 "2019-05-24T11:31:17Z")
You can find the release notes here: [https://www.elastic.co/guide/en/apm/server/6.7/release-notes.html](https://www.elastic.co/guide/en/apm/server/6.7/release-notes.html) Since 6.7 is the same major version you are using, upgrading should be straightforward. ---
**Author:** ![Barry\_Zhong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/barry_zhong/32/46786_2.png) [@Barry\_Zhong](https://discuss.elastic.co/u/Barry_Zhong)\ **Post date:** [May 28, 2019, 2:00pm UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628/6 "2019-05-28T14:00:15Z")
It works, thanks @felixbarny. ---
**Author:** ![Barry\_Zhong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/barry_zhong/32/46786_2.png) [@Barry\_Zhong](https://discuss.elastic.co/u/Barry_Zhong)\ **Post date:** [May 29, 2019, 10:52am UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628/7 "2019-05-29T10:52:32Z")
what's the plan for upgrading io.opentracing:opentracing-api:0.32.0? Since the latest apm-opentracing is only compatible with the latest Spring Cloud Opentracing on 0.2.x series ☹ ![04%20PM](https://us1.discourse-cdn.com/elastic/original/3X/4/e/4ec7e4b205349c873503b50f9fffa26ac3f2c254.png) ---
**Author:** ![felixbarny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felixbarny/32/27341_2.png) [@felixbarny](https://discuss.elastic.co/u/felixbarny)\ **Post date:** [May 29, 2019, 12:25pm UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628/8 "2019-05-29T12:25:29Z")
We have an issue for that here: [https://github.com/elastic/apm-agent-java/issues/634](https://github.com/elastic/apm-agent-java/issues/634) But note that OpenTracing is discontinued and will live on as OpenTelemetry with a completely different api. I still think it makes sense that the Java agent will have support for the final version though. But there are a lot of backwards incompatible changes which makes supporting multiple versions really difficult. While I'd like to tackle this and find solutions right away, it's difficult to prioritize this over other features ATM. ---
**Author:** ![Barry\_Zhong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/barry_zhong/32/46786_2.png) [@Barry\_Zhong](https://discuss.elastic.co/u/Barry_Zhong)\ **Post date:** [May 30, 2019, 8:27am UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628/9 "2019-05-30T08:27:45Z")
While using spring cloud gateway (reactive) and apm, we came across a weird situation as following: ![55%20PM](https://us1.discourse-cdn.com/elastic/original/3X/2/7/2799797a5e9c2b39d8f4488154313b2284735783.png) ![38%20PM](https://us1.discourse-cdn.com/elastic/original/3X/3/8/38d40fe5f210d4438cc4ed5c98b344afa263739a.jpeg) any clue? ---
**Author:** ![felixbarny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felixbarny/32/27341_2.png) [@felixbarny](https://discuss.elastic.co/u/felixbarny)\ **Post date:** [May 31, 2019, 10:19am UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628/10 "2019-05-31T10:19:41Z")
Both the Elastic APM Java agent and the reactor instrumentation propagate the context for ExecutorServices. Possibly there's something going wrong with both doing it. Could you try again with the latest snapshot (1.6.2-SNAPSHOT) of the agent? If you get the same warnings, please enable `trace` logging (set `log_level=trace`) and execute the minimum amount of requests to reproduce the problem. ---
**Author:** ![Barry\_Zhong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/barry_zhong/32/46786_2.png) [@Barry\_Zhong](https://discuss.elastic.co/u/Barry_Zhong)\ **Post date:** [June 1, 2019, 1:35pm UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628/11 "2019-06-01T13:35:26Z")
before trying that solution, I came across following error: ```auto 2019-06-01 13:33:48.066 [apm-reporter] ERROR co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Error sending data to APM server: Read timed out, response code is -1 ``` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 22, 2019, 9:35am UTC](https://discuss.elastic.co/t/incompatibility-while-using-co-elastic-apm1-6-1-and-elastic-apm-agent-1-6-1/182628/12 "2019-06-22T09:35:37Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.