Bodo,
The fix will be in the next release of STAX (which will probably be
V3.3.8) and is currently planned to be available at the end of September
(we release new versions each quarter).
If you would like a private version of the STAX Monitor with this fix, let
me know and I can make that available to you now.
Or, you can build STAX yourself as it's open source and I've already
checked the changes into CVS on SourceForge.
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
Strösser, Bodo <bodo.stroes...@ts.fujitsu.com>
07/09/2009 03:42 AM
To
Sharon Lucas/Austin/i...@ibmus
cc
"'staf-users@lists.sourceforge.net'" <staf-users@lists.sourceforge.net>
Subject
RE: [staf-users] Wrong picture on STAXMon when terminating a block
Sharon,
yes, I think this will help. Thank you very much.
I also saw some blocks disappearing from the monitor even while some
<finally> stuff was running. I guess, this will be resolved by the fix
also :-)
What version will include the fix?
Bodo
From: Sharon Lucas [mailto:luc...@us.ibm.com]
Sent: Wednesday, July 08, 2009 11:54 PM
To: Strösser, Bodo
Cc: 'staf-users@lists.sourceforge.net'
Subject: RE: [staf-users] Wrong picture on STAXMon when terminating a
block
Bodo,
I fixed the problem in the STAX Monitor so that if someone tries to
terminate a parent block that contains a finally element that is held, the
parent block and its child blocks won't "disappear", so you no longer have
to exit monitoring and then re-monitor the job to see these blocks. Note
that you won't get an error terminating a parent block as the request to
terminate the parent block was successful. It's just that the terminate
block condition is pending as it cannot complete until the child block
held by the finally element is released or terminated.
So with this bug fix the STAX Monitor will reflect the same block
information as you would get when re-monitoring the job (or when
submitting a STAX local JOB <JobID> LIST BLOCKS requests).
I hope this helps.
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
Strösser, Bodo <bodo.stroes...@ts.fujitsu.com>
06/26/2009 11:53 AM
To
"'staf-users@lists.sourceforge.net'" <staf-users@lists.sourceforge.net>
cc
Subject
[staf-users] Wrong picture on STAXMon when terminating a block
Hi,
i'm using STAX 3.3.6
I think, there is a bug in STAXMon, that can be reproduced performing the
following
steps:
- A STAX job holds the innermost block of itself using <hold/>.
- Now we kill a parent block, as we want some part of the job to be
skipped when
the block in "hold" is released.
- As soon as the parent block is terminated from STAXMon, STAXMon no
longer
displays the terminated block's childs, which I think is wrong.
- As the block in "hold" no longer is displayed, it can not be released
via STAXMon.
When the Monitor window is closed and started again, the missing blocks
are back.
Best Regards
Bodo
------------------------------------------------------------------------------
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
------------------------------------------------------------------------------
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
