Bug 1000316 - Backport of RIFTSAW-519
Summary: Backport of RIFTSAW-519
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: riftsaw
Version: 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: ---
Assignee: Julian Coleman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 986007
TreeView+ depends on / blocked
 
Reported: 2013-08-23 07:40 UTC by Adam Kovari
Modified: 2018-12-02 15:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RIFTSAW-519 0 Major Resolved Loss of recovery for BPEL process if shutdown or crash within timeout 2014-06-25 02:28:34 UTC

Description Adam Kovari 2013-08-23 07:40:02 UTC
Description of problem:
Backport of https://issues.jboss.org/browse/RIFTSAW-519 into the next Roll up patch for SOA 5.3.1 or upgrade of the Riftsaw component.

Version-Release number of selected component (if applicable):
JBoss SOA-P 5.3.1

Comment 1 Rick Wagner 2013-08-23 15:04:41 UTC
Note to Productisation / Engineering:

The non-build related commits to RIFTSAW-519 seem to be just a few lines of code, as seen at [1].

[1] https://source.jboss.org/browse/RiftSaw/dsp/branches/DSP-1.0.x/integration/jbossas5/src/main/java/org/jboss/soa/dsp/server/jbossas5/JBossServerConfigImpl.java?r=1597

--------------------------------------------------------------------------

This BZ is being suggested for a SOA-P 5.3.1 Roll up patch.  Can we please cherry-pick those few lines above and include them in the associated Roll up?

Thanks,

Rick

Comment 2 Gary Brown 2013-09-02 15:30:26 UTC
5.3.0 appears to be based on DSP 1.1.0.Final. The only change in 1.2.0.Final is the fix for RIFTSAW-519, so it looks like the easiest solution would be to move the version (and tag) of DSP used to 1.2.0.Final.

Assigning to productisation - but let me know if there is anything required.


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