Ok, I think I understand the problem: 1. @Begin does not start a new conversation until after the method completes.
2. Thus, the object I created in the method was actually outjected to the "current" conversation. 3. The conversation time out is not enforced until just prior to the redirect. So the "current" conversation is the one thats about to be timed out. 4. My outjected variable is destroyed when the "current" conversation is timed out. 5. I get a new (long running) conversation just prior to my redirect as well, one without my outjected variable. I guess what confuses me now is why doesn't seam either: a. avoid outjecting to a soon to be timed out conversations. or b. Allow the promotion of soon to be timed out conversations to long running conversations and skip the timeout. Although I can see this still being a problem for cases where you just want to use the temporary conversation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066033#4066033 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066033 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
