Hi Raj,
For starters, don't use nodes in your case. In your first example, your
main context is blocked from continuing when your action executes. In this case
your db connection in your main context is still open. You should not hold on
to open connections for so long, besides having timeouts, there are other
issues. Use states instead, and use async actions.
| <state name="x">
| <event type="node-enter">
| <action class="runAsyncAction"/>
| </event>
| <transition to="second"/>
| </state>
|
Send your process id into your action class so it will remember what
process it will send a signal when it completes. Your action should run
asynchronously, like previously suggested, or if you're just testing you can
even use a thread. When the asynchronous thread completes, signal the process
using the process id that you passed into it. Let me know if this isn't very
clear.
Regards,
Elmo
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919999#3919999
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919999
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
