Session variables persist across what?

Session variables persist across what?

• A. persist across some but not all transport barriers (VM yes, HTTP no)
• B. all transports barriers
• C. only within a single flow
• D. never across transports

Answer: (A)

Session variables hold data for the duration of the Mule session and are accessible across components and flows within the same Mule runtime. They persist across internal, in-process transports like VM because everything stays in the same runtime and shares the same session context. But when a message crosses an external transport boundary, such as HTTP, that in-memory session context isn’t guaranteed to be preserved, since HTTP exchanges are outside the runtime’s internal session flow. So they persist across some transports (VM) but not across external transports like HTTP. If you need persistence across those boundaries, you’d store the value in a persistent store or pass it along with the message as needed.

Session variables hold data for the duration of the Mule session and are accessible across components and flows within the same Mule runtime. They persist across internal, in-process transports like VM because everything stays in the same runtime and shares the same session context. But when a message crosses an external transport boundary, such as HTTP, that in-memory session context isn’t guaranteed to be preserved, since HTTP exchanges are outside the runtime’s internal session flow. So they persist across some transports (VM) but not across external transports like HTTP. If you need persistence across those boundaries, you’d store the value in a persistent store or pass it along with the message as needed.