"mmusaji" wrote : I don't mind being a guinea pig. I hope this helps other 
people who have the same issue.
  | 
Not only others, also us (creating awareness)
"mmusaji" wrote : 
  | Most of what you guys are saying is going over my head, however I think if 
the teardown waited for the process to finish this would resolve this problem 
quite quickly.
  | 
Then you at least got my main point ;-)

"mmusaji" wrote : 
  | If I wanted to do this and override the tear down method in my Junit can 
you please post an example of how I would go about this? Would be a large 
amount of code involving checking the db or is there "isAlive()" method 
somewhere?

The source of the AbstractDBTestcase is the basis. But just before deleting it, 
retrieve the processinstance based on the id, if this succeeds,, sleep, then 
retrieve it again based on the processInstance id. If this returns null, it is 
ended and you can delete it

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251593#4251593

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251593
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to