-
Notifications
You must be signed in to change notification settings - Fork 232
Can the span be made unmodifiable once finished? #334
Comments
|
@quaff do you have a sample code that would trigger this condition? |
@jpkrohling It happens occasionally when debugging and the break point in span is blocked and later resumed. |
In my case it happens on both sides of a Kafka broker: after 6 successfully sent messages the exception appear in the producer, after 3 successfully received messages same exception in the consumer. This causes the tracing info to be lost, luckily there is no impact on Kafka communications or other part of the applications for the moment. |
@jpkrohling here is my repo with the example described in my previous comment: Under the folder logs you can find the specific exception and the logs of the services. Actually the exception is the same of @quaff , I'm not using uber libraries like @yurishkuro. I hope this can help :) |
@pavolloffay After some tests I found a workaround to let everything work without any Exception on concurrency. I added just the following line in my application.properties: I know that this is just a workaround, but meanwhile you guys are fixing the issue, we can continue working on the project using the same technologies. Everything is committed in my repo posted in the previous comment. |
One user reported the exception below, which can only happen if span.log() is called concurrently with the span being processed by the reporter (i.e. after it was finished).
cc @dray92
The text was updated successfully, but these errors were encountered: