# Problem with distributing tracing for Jakarta 10 and payara 6

**URL:** <https://discuss.elastic.co/t/problem-with-distributing-tracing-for-jakarta-10-and-payara-6/372920>\
**Category:** APM\
**Tags:** java\
**Created:** [January 8, 2025, 7:59am UTC](https://discuss.elastic.co/t/problem-with-distributing-tracing-for-jakarta-10-and-payara-6/372920 "2025-01-08T07:59:41Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ciment](https://avatars.discourse-cdn.com/v4/letter/c/c37758/32.png) [@ciment](https://discuss.elastic.co/u/ciment)\
**Post date:** [January 16, 2025, 11:37am UTC](https://discuss.elastic.co/t/problem-with-distributing-tracing-for-jakarta-10-and-payara-6/372920/6 "2025-01-16T11:37:10Z")

</div>

Hi @Sylvain_Juge.

I have the same behaviour for elastic apm agent. Name for first transaction is ok, other transactions have broken name.

I tried open-telemetry agent. I have no problem to start Payara with this agent, as you mentioned before. Distributing tracing is not working for 100%, I still have a issue with asynchronous requests... but this is another topic. 🙂

I have a question about elastic java agent and this issue which is in this thread. Should I raise some ticket for Elastic Team or what is your opinion how to resolve this bug? Or Could you share this bug with your team members?

Thanks.

---

_[View the full topic](https://discuss.elastic.co/t/problem-with-distributing-tracing-for-jakarta-10-and-payara-6/372920)._