Red Hat Bugzilla – Bug 819572
jBPM ant deploy task returns 0 rc if pingServer() fails
Last modified: 2016-09-20 01:04:43 EDT
Description of problem:
A customer has noted that the ant task used to deploy jBPM3 processes will return '0' (no error) if the server it's trying to reach is unavailable. It seems more proper to return something other than 0, indicating an error.
Version-Release number of selected component (if applicable):
Deploy a process, point to an imaginary server, check $?
Please contact GSS if questions arise. Thank you.
It looks as if a change to this code might bring the desired results (if pingServer() fails, then throw an Exception):
public void execute()
throw new BuildException((new StringBuilder()).append("couldn't deploy process archives : ").append(e.getMessage()).toString(), e);
GSS prioritizes this 'medium'. There is a customer that desires the change, but it is not a production-stopping issue. If time is available, please consider implementing this small and isolated change in SOA-P 5.3.
Blocker-lite. If we don't have time, we can un-blocker this one.
Sorry - clicked wrong flag.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
If a jBPM3 process is deployed using the ant task and the server cannot be reached, a value of "0" will be returned instead of an error message. If you are trying to connect to a server and receive this value, check to make sure that the server is available before redeploying.
Closing as WONTFIX since no development (or bugfixing) is being done on jBPM 3.
Marco Rietveld <firstname.lastname@example.org> updated the status of jira JBPM-3653 to Closed