# JMS Headers

**URL:** <https://discuss.elastic.co/t/jms-headers/189095>\
**Category:** APM\
**Tags:** java\
**Created:** [July 5, 2019, 12:08pm UTC](https://discuss.elastic.co/t/jms-headers/189095 "2019-07-05T12:08:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![suikast42](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suikast42/32/29865_2.png) [@suikast42](https://discuss.elastic.co/u/suikast42)\
**Post date:** [July 5, 2019, 12:08pm UTC](https://discuss.elastic.co/t/jms-headers/189095/1 "2019-07-05T12:08:13Z")

</div>

I am testing the JMS Plugin of Java Apm Client.

The jms agent plugin creates a trace header with elastic\_apm\_traceparent instead of elastic-apm-traceparent.

```
public interface JmsInstrumentationHelper<D, M, L> {

/**
 * In some cases, dashes are not allowed in JMS Message property names
 */
public static final String JMS_TRACE_PARENT_HEADER = TraceContext.TRACE_PARENT_HEADER.replace('-', '_');

@Nullable
Span startJmsSendSpan(D destination, M message);

@Nullable
L wrapLambda(@Nullable L listener);

```

}

So the reason is clear. But that's confusing in the programming.

---

<div class="post-metadata">

**Author:** ![axw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/axw/32/28197_2.png) [@axw](https://discuss.elastic.co/u/axw)\
**Post date:** [July 6, 2019, 6:02am UTC](https://discuss.elastic.co/t/jms-headers/189095/2 "2019-07-06T06:02:42Z")

</div>

@suikast42 is there something we can do to make this less confusing? It appears to be a limitation that we need to live with.

When [https://github.com/elastic/apm/issues/71](https://github.com/elastic/apm/issues/71) is resolved (i.e. we start using the header `"traceparent"` everywhere), then I suppose this will be no longer be a problem.

---

<div class="post-metadata">

**Author:** ![suikast42](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suikast42/32/29865_2.png) [@suikast42](https://discuss.elastic.co/u/suikast42)\
**Post date:** [July 8, 2019, 6:33am UTC](https://discuss.elastic.co/t/jms-headers/189095/3 "2019-07-08T06:33:12Z")

</div>

> [@axw](#):
>
> is there something we can do to make this less confusing? It appears to be a limitation that we need to live with.

That point missed in the documentation I think.

> [@axw](#):
>
> When [Time to fully support TraceContext · Issue #71 · elastic/apm · GitHub](https://github.com/elastic/apm/issues/71) is resolved (i.e. we start using the header `"traceparent"` everywhere), then I suppose this will be no longer be a problem.

👍

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 29, 2019, 2:33am UTC](https://discuss.elastic.co/t/jms-headers/189095/4 "2019-07-29T02:33:14Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.