Closed jaimecasero closed 8 years ago
my idea is to implement it as thread interceptor in executor service
[11:30] as a background activity forthe SipAppSEssion concurrency enhancement
[11:30] there are some nice hooks , so we can take advantage of threadlocals
[11:30] which is required for proper context vars
[11:31] the hooks at that level ensure proper set/unset logic
[11:31] any other way to tackle taht is deemed to fail
[11:31] have seen it many times
[11:31] development conventions doesnt work here https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ThreadPoolExecutor.html#afterExecute(java.lang.Runnable,%20java.lang.Throwable)
Things like call-id, tx-id, or session id would be useful to have in all log traces, so a call maybe track properly along all the assigned threads...
https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/NDC.html
https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/MDC.html