This problem was resolved off-line, but I wanted to post the result to the
staf-users mailing list in case anyone else encounters this problem.
Bug #2832883 "STAX job hangs in a finally element that completes quickly"
was opened for this problem at
https://sourceforge.net/tracker/?func=detail&atid=407381&aid=2832883&group_id=33142
In a nutshell, a STAX job could hang if it contained a <finally> element
that completed very quickly (e.g. only contains a <nop/> for example).
This could occur due to a race condition within STAXFinallyAction.java
that is now fixed per this bug. This bug fix will be in the next release
of STAX, V3.3.8.
Many thanks to Bodo for finding, debugging, and resolving this problem. We
really appreciate help from people like you. Feedback and code
contributions from the community are the indispensable, invaluable
resource that will ensure the STAF project's continued success.
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
