[WFLY-11261] CLI unable to refer jberet resources after run PurgeBatc…

[nagetsum]

…hlet

Please make sure your PR meets the following requirements:

• Pull Request title is properly formatted: [WFLY-XYZ] Subject or WFLY-XYZ Subject
• Pull Request contains link to the JIRA issue(s)
• Pull Request contains description of the issue(s)
• Pull Request does not include fixes for issues other than the main ticket
• Attached commits represent units of work and are properly formatted

[wildfly-ci]

Can one of the admins verify this patch?

[jamezp]

My only concern here is performance which we may need to look into. For a small number of jobs this shouldn't be an issue.

[bstansberry]

@jamezp is hasJobExecution ok? On the surface it seems like it would be vulnerable to similar problems, since it just assumes the current children set is ok. So uses of it could provide a child Resource but then the runtime handling of that child resource might fail.

I suppose in the end in that kind of situation there's a good chance the request would fail any way, and this is just a matter of failing cleanly in Stage.MODEL with an understandable NoSuchResourceException vs failing in RUNTIME with a more obscure exception.

Anyway, as I wrote this I've convinced myself that any problem there is a different enough use case that there's no reason to mandate solving it as part of fixing this issue.

[jamezp]

@bstansberry That's a good point and IIRC the reason it was done like that was for performance. I think it takes thousands, maybe tens of thousands, of jobs before performance is an issue though.

[jamezp]

This is okay to test

[jamezp]

I've filed a separate issue as a follow up for this https://issues.jboss.org/browse/WFLY-11264

[jamezp]

this is okay to test

[jamezp]

this is ok to test