Bug 819572 - jBPM ant deploy task returns 0 rc if pingServer() fails
Summary: jBPM ant deploy task returns 0 rc if pingServer() fails
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBPM - within SOA
Version: 5.2.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Marco Rietveld
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-07 15:01 UTC by Rick Wagner
Modified: 2018-11-27 19:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2014-09-25 12:36:12 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
JBoss Issue Tracker JBPM-3653 Major Closed jBPM ant deploy task returns 0 rc if pingServer() fails 2014-09-25 12:50:18 UTC

Description Rick Wagner 2012-05-07 15:01:01 UTC
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):
SOA-P 5.2

How reproducible:
Deploy a process, point to an imaginary server, check $?


Additional info:
Please contact GSS if questions arise.  Thank you.

Comment 1 Rick Wagner 2012-05-07 15:02:15 UTC
It looks as if a change to this code might bring the desired results (if pingServer() fails, then throw an Exception):

public void execute()
                throws BuildException
            {
                try
                {
                    if(pingServerOK())
                    {
                       ...
                    }
                }
                catch(Exception e)
                {
                    throw new BuildException((new StringBuilder()).append("couldn't deploy process archives : ").append(e.getMessage()).toString(), e);
                }
            }

Comment 2 Rick Wagner 2012-05-07 15:12:39 UTC
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. 

Thanks,

Rick

Comment 3 Rick Wagner 2012-05-31 19:11:09 UTC
Blocker-lite.  If we don't have time, we can un-blocker this one.

Comment 5 David Le Sage 2012-06-12 03:50:07 UTC
Sorry - clicked wrong flag.

Comment 6 Suz 2012-06-12 04:08:29 UTC
    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.
    
    New Contents:
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.

Comment 7 Marco Rietveld 2014-09-25 12:36:12 UTC
Closing as WONTFIX since no development (or bugfixing) is being done on jBPM 3.

Comment 8 JBoss JIRA Server 2014-09-25 12:50:18 UTC
Marco Rietveld <marco.rietveld@redhat.com> updated the status of jira JBPM-3653 to Closed


Note You need to log in before you can comment on or make changes to this bug.