Bug 1168746 - [DROOLS-650] Please fix the issue of broken Sequential Phreak for BRMS 6.x
Summary: [DROOLS-650] Please fix the issue of broken Sequential Phreak for BRMS 6.x
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.0.3
Hardware: All
OS: All
medium
medium
Target Milestone: ER4
: 6.1.0
Assignee: Mario Fusco
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks: 1168747 1175886 1179906
TreeView+ depends on / blocked
 
Reported: 2014-11-27 17:36 UTC by Musharraf Hussain
Modified: 2020-03-27 20:12 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
: 1168747 1175886 (view as bug list)
Environment:
Last Closed: 2020-03-27 20:12:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker DROOLS-650 0 Major Resolved Sequential Phreak is broken 2016-08-04 10:06:44 UTC

Description Musharraf Hussain 2014-11-27 17:36:17 UTC 
Description of problem:
- Please add the fix for the issue of broken Sequential Phreak in future BRMS 6.x releases, which has already been fixed in the community as part of this JIRA [1] and commit [2] .

[1] https://issues.jboss.org/browse/DROOLS-650
[2] https://github.com/droolsjbpm/drools/pull/397

Version-Release number of selected component (if applicable):
- BRMS 6.0.3

How reproducible:
- NA

Steps to Reproduce:
1. NA
2.
3.

Actual results:
- NA

Expected results:
- NA

Additional info:
- NA
Comment 2 Mario Fusco 2014-11-27 17:52:50 UTC 
Fixed on 6.0.x branch by https://github.com/droolsjbpm/drools/commit/ea34160260e4ca98b59e62104d836d4ad7b0b31a
Comment 3 jvahala 2014-12-17 09:44:41 UTC 
Commit is present, verified.
Comment 4 Ryan Zhang 2014-12-25 01:42:25 UTC 
This issue is for rollup#2, not 6.1. 
Moving the status back to MODIFIED.
Comment 5 jvahala 2015-01-22 12:35:58 UTC 
Ryan, this issue is for 6.1, for rollup#2 is 
https://bugzilla.redhat.com/show_bug.cgi?id=1175886

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