https://github.com/gtiwari333/sleuth-jms-broken-tracing

https://github.com/gtiwari333/sleuth-jms-broken-tracing

Last synced: about 2 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/gtiwari333/sleuth-jms-broken-tracing
• Owner: gtiwari333
• Created: 2020-08-04T22:56:40.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2024-03-13T18:58:54.000Z (10 months ago)
• Last Synced: 2024-10-13T02:18:53.883Z (3 months ago)
• Language: Java
• Homepage:
• Size: 136 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 2
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# sleuth-jms-broken-tracing

GIT Project for issue : https://stackoverflow.com/questions/63257909/spring-sleuth-broken-tracing-on-jms-errorhandler

```

2020-08-04 17:55:24.212  INFO [,225c47fb814f6584,225c47fb814f6584,true] 16956 --- [nio-8080-exec-1] sleuth.SleuthApplication                 : Queuing message ...

2020-08-04 17:55:24.282  INFO [,225c47fb814f6584,eac851f1650ae8a6,true] 16956 --- [enerContainer-1] sleuth.SleuthApplication                 : JMS message received SOME MESSAGE !!!

2020-08-04 17:55:24.321  INFO [,225c47fb814f6584,612a7956f6b29a01,true] 16956 --- [nio-8080-exec-3] sleuth.SleuthApplication                 : test1 called  <<<<<<<<< FINE UPTO HERE

2020-08-04 17:55:24.332  INFO [,,,] 16956 --- [enerContainer-1] sleuth.SleuthApplication                 : handling error by calling another endpoint ..     <<<<<<<<< new thread started and lost tracing

2020-08-04 17:55:24.336  INFO [,4c163d0997076729,4c163d0997076729,true] 16956 --- [nio-8080-exec-2] sleuth.SleuthApplication                 : test1 called  <<<<<<<<< new trace id received

```

## Solution (a workaround) found:

See the diff on the PR:

https://github.com/gtiwari333/sleuth-jms-broken-tracing/pull/2/files