Bug 819572
| Summary: | jBPM ant deploy task returns 0 rc if pingServer() fails | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Rick Wagner <rwagner> |
| Component: | JBPM - within SOA | Assignee: | Marco Rietveld <mrietvel> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.2.0 GA | CC: | dlesage, ldimaggi, mvecera, sdorfiel, smcgowan, soa-p-jira |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-09-25 12:36:12 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Rick Wagner
2012-05-07 15:01:01 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);
}
}
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 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.
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.
Closing as WONTFIX since no development (or bugfixing) is being done on jBPM 3. |