Weblogic JMS EJB : ThreadLocal access query : getting null in same thread

Question

We have two applications(one is jms and other is ejb) on single instance of weblogic managed server.
On receving a new jms message the jms application call the ejb application by passing the new xml message.
ejb application creates a threadlocal object and allocated transaction id to this transaction. I want to access this transactionid(present in threadlocal) in my jms application. But i am getting null.
I believe i am in the same thread as i printing the thread number in the both the application log. I verified that same thread number was present for multiple messages
in both logs [Except if one scenario of thread pooling is present that when jms calls ejb it frees the thread(23) and when ejb completes its job if gives back the thread(23) to jms...but it resets thread local]
I need answer to following question
1. Why is my transaction id null when i access through jms application.
2. I believe i am in the same jvm instance.
3. I believe i am in the same thread instance...( looking at logs except if someone can tell me i am not.....)
4. Or if there is alternative solution to pick up threadlocal variable in my jms application.
JMS application is new application trying to connect to existing ejb application which had the thread local design and we want to use that existing architecture before we decide to change. We need the transactionid for log corelation.

Answer 1

I assume that either your JMS destination is backed by a database or your application is doing some database operations in the same transaction as the JMS send operation. I suspect that there is some kind of database maintenance process going on every night, which causes the database operations to be slow or not responding, which in turn causes the MDB transaction that the JMS send operation participates in to timeout.